Re: [w3c/webcomponents] [idea] Allow HTML Element attributes to accept any type of value, not just strings. (#519)

Here's a live example: http://trusktr.io/polydance (open in Chrome, may not yet work in other browsers)

Here's the part of source code where the 3D scene is described declaratively: 

https://github.com/trusktr/trusktr.io/blob/master/meteor-app/client/imports/apps/polydance.js#L193-L331

I will be hacking `setAttribute` and seeing what difference skipping number-to-string-to-number conversion may have. Maybe depending on the use case that part isn't a bottle neck. I am just looking to find any way to improve performance. I probably have lots of improvements to make on the WebGL structures.

-- 
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/519#issuecomment-322835836