Firebase Messaging & Microsoft Edge 42 (VAPID)

[Marcel Dopita]

Hello,

Starting with Microsoft Edge version 42 (which is already available in insiders previews), it will support all required features for delivery of push notifications (Notifications, Service Workers, Web Push API, VAPID). https://blogs.windows.com/msedgedev/2017/12/19/service-workers-going-beyond-page/

Can we expect Microsoft Edge to be supported by Firebase Messaging (just like Firefox is)? We already use FCM because of Android and take advantage of its support on iOS/Chrome/Firefox. I understand that we can achieve Edge support by pure VAPID implementation but my understanding is that Firebase already leverages that in Firefox and so in theory the same should apply for Edge (?).

I quickly tried Firebase Messaging (version 4.8.1) and it asked for notification permission but it didn't work (I saw no error in console but was unable to properly debug FCM service worker). I'm also not sure if Firebase depends on any features not yet available in Edge 42 (like TextEncoder).

Regards,

Marcel

[Matt Gaunt]

In theory it should work (i.e. there is no reason it shouldn't) and under the hood FCM is using VAPID.

I don't have access to a Windows Machine that I can load up with insider program - so if anyone is aware of a way to virtualize this or can provide further input as errors / debugging, it would be greatly appreciated. 

Worth noting, the source code for the FCM SDK on web is here: https://github.com/firebase/firebase-js-sdk

Cheers,

Matt