Isn't there a risk of conflict with elements introduced in future versions of HTML?
X-Tag - a cross-browser web components library
11–20 of 54 posts
Re: X-Tag - a cross-browser web components library
#12Isn't there a risk of conflict with elements introduced in future versions of HTML?
Re: X-Tag - a cross-browser web components library
#13Re: X-Tag - a cross-browser web components library
#14Why won't the poly fill work in IE9
Because it doesn't support CSS Animations, which I use for insertion detection. I might be able to finagle it for IE9 with Mutation events, but in their DOM Level 3 state, they destroy performance. IE10 supports CSS Animations and will also be the first IE version to support HTML5 Windows apps, those are the two most significant reasons it is the current minimum version for IE. If IE9 is the thing people really need,…
Re: X-Tag - a cross-browser web components library
#15Earlier quoted context omitted.
Because it doesn't support CSS Animations, which I use for insertion detection. I might be able to finagle it for IE9 with Mutation events, but in their DOM Level 3 state, they destroy performance. IE10 supports CSS Animations and will also be the first IE version to support HTML5 Windows apps, those are the two most significant reasons it is the current minimum version for IE. If IE9 is the thing people really need,…
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.
Re: X-Tag - a cross-browser web components library
#16Re: X-Tag - a cross-browser web components library
#17Re: X-Tag - a cross-browser web components library
#181. 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
Re: X-Tag - a cross-browser web components library
#19The 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
Another huge benefit: the polyfill is 2k compressed composed of pure, library-independent JS
Re: X-Tag - a cross-browser web components library
#20The 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