A reminder that if Mozilla can build Firefox's entire UI in Web Components, and if Chromium browsers can power a huge fraction of the UI with them, they're good enough for your website.
-
A reminder that if Mozilla can build Firefox's entire UI in Web Components, and if Chromium browsers can power a huge fraction of the UI with them, they're good enough for your website.
-
@slightlyoff I cannot even create a custom <RectWithLabel> svg component, since svg namespace does not allow it.
-
-
@slightlyoff not entire ui, there’s some react in there too, for example the devtools if i remember correctly
-
@slightlyoff What if my website targets Netscape Navigator 2?
-
@botahamec I guess stick with React? It won't work, but just like React's IE 9-11 "support", nobody's actually testing on it, so you won't get bug reports. And it will at least feel like you tried! I am told that's a fine substitute for resilient progressive enhancement.
-
@actualwitch Everyone makes mistakes. We're deep into cleaning up ours right now:
https://thenewstack.io/from-react-to-html-first-microsoft-edge-debuts-webui-2-0/