Server-Sent Events (EventSource)
Enables push notifications from the server received as DOM events.
Jonathan Sampson [MSFT]
shared this idea
103 comments
-
Sanders
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.
-
Anonymous
commented
I basically tell people not to use Microsoft Edge.
-
Daniele commented
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.
-
6340
commented
Microsoft, why?
-
6340
commented
**** yah!
-
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.
-
John
commented
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.
-
Lars Kemmann
commented
It may be "legacy" but it's a proven piece of web infrastructure that makes very efficient use of existing technologies. I greatly prefer the simplicity of SSE over something like Web Sockets -- a heavyweight bolt-on that certainly has its place but, as mentioned by others, comes with a lot of overhead and risk: firewalls, complexity, etc.
-
Sergey Rubanov
commented
Seems like SSE is considered as legacy by whatwg team
https://github.com/whatwg/html/issues/2177 -
Ryan Hanthorn
commented
Edge has unfortunately lagged behind every other browser in terms of implementing standard features. I'm a big fan of standards and I'm not going to spend a huge number of dev hours compensating for a lack of standard features every other browser supports but one. So officially, I don't support Edge. But, I would like to.
This feature in particular is necessary to easily develop real time sites. I'd very much like to see it implemented as soon as possible.
-
Fábio Alves commented
I need this amazing feature. It made my development richer in Chrome but sadder in Edge.
-
Andy
commented
@John
please, only remove Safari from your list of "modern" browsers, because it supports even less standards than Edge, it's on the level of IE11 that already outdated and is not being developed
Whichever feature I check on caniuse.com and test - there is a big chance that it doesn't work in Safari -
John
commented
SSE has been supported by most browsers for 6 years already, can't believe a highly requested feature of a simple Web Standard takes so long for Microsoft to implement. Inability like this makes me wish Edge never existed and Microsoft just stopped making web browsers altogether.
The Internet would be a more modernized and much better off if IE/Edge no longer exist and we only needed to support Chrome, Safari, Firefox and Opera.