3 ms·
web components are standard, and have been for a long while. Virtually no one uses lynx, and it's not anyone else's fault that lynx has lagged on implementing
by colordrops 3y ago
web components are standard, and have been for a long while. Virtually no one uses lynx, and it's not anyone else's fault that lynx has lagged on implementing long-existing web standards.
- lcnPylGDnU4H9OF 3y agoIf anyone gets here confused, I left this comment above because I mistook who I was replying to: I’m curious: does it work in Lynx[0]? I assume no because there’s no executed javascript, which is required to register the component as far as I know. It’s worth stating the point in a different way. Even one person using such a browser “matters”, in a way, and it’s good to be kind when one can. (Apologies if this comes off as harsh; however, it does seem to me that the other commenter has a point, at least in their second comment.) 0: https://en.wikipedia.org/wiki/Lynx_(web_browser) https://en.wikipedia.org/wiki/Lynx_(web_browser) ---- “Virtually no one” does sound a lot like someone. Per this point of “browsers that matter”, many people will also say “accessibility matters”. Support of Lynx is a worthwhile goal in regard to web accessibility, in no small part because it does not execute javascript.