X-Tag - a cross-browser web components library

Re:X-Tag - a cross-browser web components library by politician on Friday June 15, 2012 @09:19PM (#4119570)

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!

[ Parent | on HN ]

Re:X-Tag - a cross-browser web components library by Navarr on Saturday June 16, 2012 @02:03PM (#4121168)

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.

[ Parent | on HN ]

Re:X-Tag - a cross-browser web components library by dandonkulous on Monday June 18, 2012 @10:14AM (#4126490)

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.

[ Parent | on HN ]