3 ms·

The naming is unfortunate. But also, it'd be pretty cool if this was implemented as a browser extension, that way it could be much faster to iterate over. I w

The naming is unfortunate. But also, it'd be pretty cool if this was implemented as a browser extension, that way it could be much faster to iterate over. I wonder why this is not common practice? Modifying browser internals is such a pain that it strikes me as odd that it is the 1 established way of going about this proposals.

zodiakzz 5y ago
If I am not wrong, a functional version can be written in plain JS (+ WASM?) using Custom Elements (tho tag names must contain a hyphen). Except I don't know why all the non-Google stakeholders are hell bent on sabotaging Custom Elements. While Google is doing so much innovation in that space. Strange.
- kreetx 5y ago
  Came here to say that. They could do a custom element implementation, perhaps ship that (in their own namespace), offer polyfills for other browsers and go on from there.
- pjmlp 5y ago
  Not only it can, it already exists. https://modelviewer.dev/ https://modelviewer.dev/