X-Tag - a cross-browser web components library • Hacker News Board

Re: X-Tag - a cross-browser web components library

#51

Post by fwenzel » Sun, Jun 17, 2012, 3:35 PM UTC

hcarvalhoalves wrote: post #45

Ok, so is this like -vendor, but for HTML? Now browsers can implement their own components and, hopefully, push it as a standard?

Browsers were always able to implement their own tags. x-tag allows the developer of a website to write their own tags (and share them with others, etc.), which is huge.

Re: X-Tag - a cross-browser web components library

#52

Post by dandonkulous » Mon, Jun 18, 2012, 2:14 PM UTC

Navarr wrote: post #49

politician wrote: post #35

Earlier quoted context omitted.

X-Tags could be made self-hosting with a name registry and a simple "missing x-tag" tag. In other words, 1. Visit the registry for a tag. 2. Start using it in your markup. Assuming the registry's CDN is available, of course!

While I considered this approach to be plausible at first glance, it isn't. For the tags to work for your users, they would also have to visit the registry for that tag.

I actually think a spin on this idea could work, we're going to be working with Google on adding a tag library to their JS libraries CDN (that is tentative btw) and the spec already calls for multi-tag definition inclusion via link tag.

Re: X-Tag - a cross-browser web components library

#53

Post by edwinyzh » Mon, Jun 18, 2012, 4:00 PM UTC

This sounds great! Can anybody compare it with angularjs (by Google)?

Re: X-Tag - a cross-browser web components library

#54

Post by dandonkulous » Tue, Jun 19, 2012, 6:53 PM UTC

MatthewPhillips wrote: post #36

legutierr wrote: post #34

Earlier quoted context omitted.

I, for one, would never use this while it remains incompatible with a large segment of the web-browsing public. So, yes, I think it would be a big deal. IE8 would be even better. But with IE9 compatibility, at least it would be feasible to start using this when IE8 fades away.

I'm not sure IE9 is such a huge win. This already supports IE10, and every Windows 7 computer will be auto-updated to IE10 (if Microsoft holds to it's decision to automatically update from now on). XP users will never get IE9 or IE10, and IE8 can't be supported unfortunately. So I guess Chrome Frame will be necessary to target IE8 users.

IE9 support lands today, and we've decided against supporting earlier versions of IE - too much headache and code bloat/hackishness to justify addressing the ever shrinking < IE9 user base.