Re:X-Tag - a cross-browser web components library
by gliese1337 on Saturday June 16, 2012 @03:54AM
(#4120113)
So, how does this impact Web Components? It seems to fill pretty much the exact same role, but with a rather different implementation. Should I expect to see this become the new standard because there's a polyfill for it so people will start using it already, or am I gonna end up with a bunch of legacy code when something else becomes standardized? And, again like Web Components, it's duplicating functionality that's been in Internet Explorer of all places since IE5.0 with DHTML Behaviors.
[ Parent
| on HN ]
Re:X-Tag - a cross-browser web components library
by dandonkulous on Saturday June 16, 2012 @07:13AM
(#4120370)
Actually I have been meeting with the W3 Web Components spec author for about 2 months while we readied this. The document.register method that was recently added to the spec was in large part a byproduct of X-Tag and when browsers implement it (Firefox soon) X-Tag will use it internally in browsers that support it, as a polyfill always does. Once one browser implements the JS mentod, X-Tag will truly polyfill the method on document as well.
Re:X-Tag - a cross-browser web components library
by rmc on Saturday June 16, 2012 @06:06AM
(#4120291)
I'm not sure, but I think this is 'Web Components'. The Mozilla page says so https://wiki.mozilla.org/Apps/x-tag