Server-Sent Events (EventSource)
Enables push notifications from the server received as DOM events.
John Michael Snook commented
And this is why I tell my clents to use FF or chrome.
SSE is a must in any major browser, but it doesn't make sense that Microsoft Edge can't until now support such an important feature
I'm huge fan of MS, and I use Edge.
But you make it hard for me...
Davy Van Roy commented
Was surprised it is not supported on Edge, this is long overdue given all other browser do support it...
Artem Shamsutdinov commented
There's something seriously lacking in Edge's dev team if they're unable to implement a simple standards-based feature other (aka modern) browsers have implemented over 1/2 a decade ago. Whilst implementing Server Sent Events is way overdue, everyone would be better off if Edge stops holding back the web and just adopts another browser engine since it's clear their dev team is unable to keep up with teams on other browsers.
I basically tell people not to use Microsoft Edge.
I don't understand why. Anyway, hope to see it soon.
Dan Jarvis commented
I am seriously shocked to land here, being 2017, to learn of no SSE for Edge. Seriously? Holy ****. I thought Microsoft was over this whole "let's be that weird substandard browser with awkward workarounds" type of thing. SSE has been around for a long time and is often favored other other more complicated solutions.
Dave Elliott commented
Developing major IoT application to be used world-wide... will tell users not to use Microsoft browsers due to lack of SSE.
Eric Grange commented
Lack of support for SSE is embarassing after all these years and all those votes.
Polyfills just result in pounding the servers with polling requests. Websockets do not scale as well as SSE.
So here, IE/Edge users end up with degraded functionality, and a message to switch to a more "mainstream" browser.
Please add this, im web dev and im sad when i need to call my users to use other browsers (Chrome, FF, Opera, Safari etc.)
Lars Kemmann commented
Yes, absolutely please also add the custom headers support described in the WHATWG HTML spec GitHub issue that @Sergey and @Matthias mention. This simple addition to a well-established standard can breathe fresh life into an already-excellent concept: "a really nice *standard* for implementing simple web-based queue-consumers with out of the box at least once consumption semantic" -- which is a critical building block for modern reactive web apps.
Matthias Kurz commented
Yes, please consider https://github.com/whatwg/html/issues/2177#issuecomment-314401181
Would be great to finally get this into Edge.
Sergey Rubanov commented
please consider https://github.com/whatwg/html/issues/2177#issuecomment-314401181!
René Mercure commented
Many shared servers do not allow use of websocket, but do work perfectly with SSE.
whatwg should reconsider the "legacy" status of that feature and Edge should speed up the development of this feature as they'll lose support from many websites.
Mauro Pereira Junior commented
Currently, if you open our application in Edge it will show the following message:
"THIS APP IS ONLY SUPPORTED BY CHROME, FIREFOX AND SAFARI"
This happens only because of the lack of SSE feature in the Edge Browser.