178940 2017-10-27 09:22:11 -0700 [Service Worker] Support passing MessagePort objects to postMessage() 2018-02-01 09:12:07 -0800 1 1 1 Unclassified WebKit WebCore Misc. WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 181178 https://bugs.webkit.org/show_bug.cgi?id=174541 InRadar P2 Normal --- 1 cdumez cdumez beidson coertzen.jfs ggaren olivier thiago.soares webkit-bug-importer youennf oldest_to_newest 1365377 0 cdumez 2017-10-27 09:22:11 -0700 Support passing transferables (such as MessagePort objects) to postMessage(). 1365378 1 webkit-bug-importer 2017-10-27 09:22:44 -0700 <rdar://problem/35222245> 1389479 2 youennf 2018-01-16 01:21:02 -0800 *** Bug 181648 has been marked as a duplicate of this bug. *** 1395167 3 thiago.soares 2018-01-31 14:53:41 -0800 We have a product that uses the Service Worker Api and also need to pass MessagePort objects to postMessage(). It is a feature that will block us from using our solution on Safari. 1395172 4 cdumez 2018-01-31 14:59:54 -0800 Oh, this has actually been implemented. *** This bug has been marked as a duplicate of bug 181178 *** 1395203 5 youennf 2018-01-31 15:48:22 -0800 (In reply to Thiago Soares from comment #3) > We have a product that uses the Service Worker Api and also need to pass > MessagePort objects to postMessage(). > It is a feature that will block us from using our solution on Safari. Thiago, do you have a public endpoint for your solution that we could use for our testing? Can you detail your usage of MessageChannel? Do you have any other requirement in terms of service worker features that Safari Tech Preview 47 would not fulfill? 1395337 6 coertzen.jfs 2018-01-31 21:21:55 -0800 https://mdmobile.co.za, you'll need a username and password for the update to start though. Can't you test it yourself? The issue is passing information through postMessage to the Service Worker. 1395477 7 youennf 2018-02-01 08:34:25 -0800 (In reply to Stephan Coertzen from comment #6) > https://mdmobile.co.za, you'll need a username and password for the update > to start though. Can't you test it yourself? The issue is passing > information through postMessage to the Service Worker. Sure, we are testing this particular feature. It is always good to do some field testing as well :) Also, it is a different matter if what is blocking your web site from supporting WebKit is just postMessage or if you need other stuff like pushManager, openWindow(), focus()... 1395483 8 coertzen.jfs 2018-02-01 08:51:12 -0800 I would think that you are implementing the service worker for all scenarios according to standard. Our App has been built to conform to standard to be supported by all browsers. https://www.w3.org/TR/service-workers-1/#dom-serviceworker-postmessage So no, this would not be the only thing that our PWA would need. 1395489 9 thiago.soares 2018-02-01 08:59:14 -0800 (In reply to youenn fablet from comment #5) > (In reply to Thiago Soares from comment #3) > > We have a product that uses the Service Worker Api and also need to pass > > MessagePort objects to postMessage(). > > It is a feature that will block us from using our solution on Safari. > > Thiago, do you have a public endpoint for your solution that we could use > for our testing? Can you detail your usage of MessageChannel? Do you have > any other requirement in terms of service worker features that Safari Tech > Preview 47 would not fulfill? Hi Youenn, We have a beta environment that I can give you access if you want. I will contact you on your email. We use the MessageChannel to enable the service worker to directly respond to a message sent by the application: Application code: var messageChannel = new MessageChannel(); messageChannel.port1.onmessage = handleCommandResponse swReg.active.postMessage(message, [messageChannel.port2]); SW Code: onMessage: function(event) { } 1395498 10 youennf 2018-02-01 09:11:34 -0800 (In reply to Stephan Coertzen from comment #8) > I would think that you are implementing the service worker for all scenarios > according to standard. Our App has been built to conform to standard to be > supported by all browsers. > https://www.w3.org/TR/service-workers-1/#dom-serviceworker-postmessage > > So no, this would not be the only thing that our PWA would need. I am also interested in having a fully compliant service worker implementation. WebKit is not there yet. Current focus is on making sure fetch event, offline mode, network proxy use cases will work fine. 1395500 11 youennf 2018-02-01 09:12:07 -0800 (In reply to Thiago Soares from comment #9) > (In reply to youenn fablet from comment #5) > > (In reply to Thiago Soares from comment #3) > > > We have a product that uses the Service Worker Api and also need to pass > > > MessagePort objects to postMessage(). > > > It is a feature that will block us from using our solution on Safari. > > > > Thiago, do you have a public endpoint for your solution that we could use > > for our testing? Can you detail your usage of MessageChannel? Do you have > > any other requirement in terms of service worker features that Safari Tech > > Preview 47 would not fulfill? > > Hi Youenn, > > We have a beta environment that I can give you access if you want. I will > contact you on your email. Thanks Thiago, that would be helpful.