Live data from Hacker News

X-Tag - a cross-browser web components library

mozilla.github.com

31–40 of 54 posts

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

#31

Earlier quoted context omitted.

This really makes me sad. Mutation events gets you to IE9 but not 8, which means this cannot be used for enterprise apps. I'll start using it in personal projects though. Love the work.

Yeah the funny thing is I could actually even make it work in IE6 and 7 if I used Mutation for IE9 and then - ready your pitchforks and torches folks - proprietary CSS Behavior script ducks to avoid tomato . IE8 screwed the pooch in this regard - they removed CSS Behaviors but failed to implement anything that could be used to do the same sort of thing.

Do it, because without IE7 or at least IE8 support this will barely get used.

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

#33
post #31

Earlier quoted context omitted.

Yeah the funny thing is I could actually even make it work in IE6 and 7 if I used Mutation for IE9 and then - ready your pitchforks and torches folks - proprietary CSS Behavior script ducks to avoid tomato . IE8 screwed the pooch in this regard - they removed CSS Behaviors but failed to implement anything that could be used to do the same sort of thing.

Do it, because without IE7 or at least IE8 support this will barely get used.

I'm going to work on it this weekend!

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

#34

If I can get it compatible with IE9, is that a big thing for people here? I don't think it would be too hard, thoughts?

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.

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

#35
post #18

The steps seem pretty dishonest to me. Correct me if i'm wrong, but these are the real X-Tag steps: 1. Scour the web for a plugin 2. Add the plugin script include to your page 3. Copy/Type the new HTML tag 4. Customise the plugin with your own behavior 5. Wash, Rinse, & Repeat

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!

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

#36

If I can get it compatible with IE9, is that a big thing for people here? I don't think it would be too hard, thoughts?

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.

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

#39
post #38

Doesn't work on the Arch Linux build of Firefox. Tested both in safe mode and in a new profile. However, the Mozilla build works fine.

Can you file a bug (at bugzilla.mozilla.org) and CC me (":khuey")? I'd like to figure out what Arch is doing here.
Post reply on HN