17 ms·
What are you using that Edge doesn't support? We treat Chrome/Safari/Edge/FF all as 1st class browsers and haven't had many problems (aside from Safari lacking
by dan1234 7y ago
What are you using that Edge doesn't support?
We treat Chrome/Safari/Edge/FF all as 1st class browsers and haven't had many problems (aside from Safari lacking U2F and exotic CSS props like motion-path).
- chrismorgan 7y agoA few things I’ve been using without EdgeHTML support: #rgba and #rrggbbaa in CSS, <details>, Custom Elements v1. On my personal website, I have deliberately chosen to no longer polyfill these or change my process to avoid #rgba in the final CSS, so various background colours are missing, the light/dark theme switcher doesn’t collapse (it should start collapsed), and a terminal recording will be missing in an upcoming blog post. mix-blend-mode is another thing that EdgeHTML doesn’t support that I was using for a bit, but I stopped using it because I kept finding critical bugs with it in Chromium, most notably https://bugs.chromium.org/p/chromium/issues/detail?id=992398 https://bugs.chromium.org/p/chromium/issues/detail?id=992398 which was impossible to work around, simply stopping rendering the page after 8192px!
- ataylor32 7y agoA few issues I have run into with Edge: 1. The :focus-within CSS pseudo-class doesn't work 2. object-fit only works on images 3. These SVG loaders don't work: https://samherbert.net/svg-loaders/ https://samherbert.net/svg-loaders/
- simongray 7y agoDamn, lacking :focus-within is a big one. That pseudo-selector is very useful when creating custom widgets.