Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)

WebGL fragment and vertex examples:

**trusted sources**
https://www.html5rocks.com/en/tutorials/webgl/webgl_fundamentals/
https://www.khronos.org/webgl/wiki/Tutorial

**how users do that anyway**
https://github.com/mrdoob/three.js/issues/283
http://stackoverflow.com/questions/4878145/javascript-and-webgl-external-scripts
https://blog.mayflower.de/4584-Playing-around-with-pixel-shaders-in-WebGL.html

Can they do it differently? Yes.
Will they? Probably no, they don't care, `script` works already like a charm.

What would `is` solve for them?
It'd be a better way to bootstrap shaders without needing to pollute the global context with unique IDs all over.

Does it mean we probably just need a native mechanism to bootstrap once some native element on the DOM? Most likely, and coincidentally, `is` does that **too**.

Best Regards



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/509#issuecomment-261898480