search

webcomponents / webcomponents.github.io

WebComponents.org is where community-members document Web Components best practices
http://webcomponents.org
735 stars 126 forks source link

Update Browser Support #329

Open Nevraeka opened 8 years ago

Nevraeka commented 8 years ago
Nevraeka commented 8 years ago

cc @robdodson @csuwildcat

robdodson commented 8 years ago

I'm not sure what the color codes mean but I think everything that is currently red for custom elements / shadow dom should be set to yellow since everyone is either actively working on those and some folks have already shipped them in preview.

I think HTML Imports should be the only red squares.

Mobile browser support would be cool to include. Might make the table kinda long though?

Nevraeka commented 8 years ago

@robdodson I agree on the mobile browsers. I was thinking we could either make the images smaller and have 2 rows or just say we support the latest mobile versions of these as well as the desktop versions

As for yellow on Shadow DOM - are we sure about active development in all browsers or has it been scheduled but work has not started yet ?

robdodson commented 8 years ago

In Safari I'm pretty sure they're actively prototyping Custom Elements (there's a ticket...somewhere) and Shadow DOM v1 just shipped in Safari Technology Preview.

As for Edge... @csuwildcat any updates on that?

Nevraeka commented 8 years ago

What about IE(9-10) support? Is that still necessary? We absolutely need 11 but I wonder if the polyfills has evolved recently. I would think so but IDK

csuwildcat commented 8 years ago

@robdodson it is in the queue, but behind Service Worker development - they're just a bit backed up at the moment.

robdodson commented 8 years ago

@Nevraeka I don't think there's any plan to work on IE9-10 support in either webcomponentsjs or polymer.

csuwildcat commented 8 years ago

@robdodson IE9-10 combine for almost 10% of global market share, from my quick look - which seems rather significant. Web Components JS doesn't offer support for browsers that low, but we added a couple small API polyfills to our distribution that enable it, and we haven't had issues (with Custom Elements, not Shadow DOM)

robdodson commented 8 years ago

oh sorry, not saying it's not an important sector, I just don't think anyone (on our end at least) has the availability to work on supporting it.

we added a couple small API polyfills to our distribution that enable it, and we haven't had issues (with Custom Elements, not Shadow DOM)

Related to x-tag?

csuwildcat commented 8 years ago

@robdodson yeah, we get IE9-10 support for the non-Shadow DOM specs just by including a DOMTokenList polyfill

robdodson commented 8 years ago

@csuwildcat would you want to vend those custom element polyfills on webcomponents.org with instructions on how to use them?

Nevraeka commented 8 years ago

👍 to

@csuwildcat would you want to vend those custom element polyfills on webcomponents.org with instructions on how to use them?

good call @robdodson . I want to update the resources page asap anyway and thats a great place for these

Nevraeka commented 8 years ago

From a Shadow DOM perspective @treshugart (SkateJS) & @eisenbergeffect (Aurelia) both have polyfills for named-slots for Shadow DOM v1 . It might make sense to work together toward a common project on these polyfills. Thoughts @csuwildcat or @robdodson ?

csuwildcat commented 8 years ago

I suppose the first step would be to setup a shared set of tests that each implementation can run against the same criteria. @robdodson, is there a current set of tests that are easy to run against other polyfill implementations?

On Fri, May 27, 2016 at 11:31 AM, Erik Isaksen notifications@github.com wrote:

From a Shadow DOM perspective @treyshugart (SkateJS) & @eisenbergeffect https://github.com/eisenbergeffect (Aurelia) both have polyfills for named-slots for Shadow DOM v1 . It might make sense to work together toward a common project on these polyfills. Thoughts @csuwildcat https://github.com/csuwildcat or @robdodson https://github.com/robdodson ?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/webcomponents/webcomponents.github.io/issues/329#issuecomment-222220968, or mute the thread https://github.com/notifications/unsubscribe/AAICypWvELUhw4RObes7vIPZ14yV2w3-ks5qFziQgaJpZM4IZdBR .

robdodson commented 8 years ago

Good question. @azakus @addyosmani do you know of any SD unit test suite?

On Fri, May 27, 2016 at 11:38 AM, Daniel Buchner notifications@github.com wrote:

I suppose the first step would be to setup a shared set of tests that each implementation can run against the same criteria. @robdodson, is there a current set of tests that are easy to run against other polyfill implementations?

On Fri, May 27, 2016 at 11:31 AM, Erik Isaksen notifications@github.com wrote:

From a Shadow DOM perspective @treyshugart (SkateJS) & @eisenbergeffect https://github.com/eisenbergeffect (Aurelia) both have polyfills for named-slots for Shadow DOM v1 . It might make sense to work together toward a common project on these polyfills. Thoughts @csuwildcat https://github.com/csuwildcat or @robdodson https://github.com/robdodson ?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/webcomponents/webcomponents.github.io/issues/329#issuecomment-222220968 , or mute the thread < https://github.com/notifications/unsubscribe/AAICypWvELUhw4RObes7vIPZ14yV2w3-ks5qFziQgaJpZM4IZdBR

.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/webcomponents/webcomponents.github.io/issues/329#issuecomment-222222556, or mute the thread https://github.com/notifications/unsubscribe/ABBFDQ4bI-fRyR68kS_FPXPAFQPQ7Wrcks5qFzomgaJpZM4IZdBR .

treshugart commented 8 years ago

We have a set of tests for the DOM API that @nadiam84 has been doing quite a bit of work on but it's not exhaustive.

FWIW, our polyfill is a polygap / prollyfill. We only intend on supporting the JavaScript API - which is a must-have for integration with React and other virtual DOM libraries - but CSS support is a nice to have for us and isn't worth the page weight and performance hit. IE9 is supported.

Happy to do anything we can to collaborate on this stuff.

robdodson commented 8 years ago

It looks like there's a number of tests living in the webcomponents.js repo that use WebComponentTester https://github.com/webcomponents/webcomponentsjs/tree/master/tests

miguelamello commented 8 years ago

Polymer 1.0 is not working properly in IE 11.0.9600.18314 Many average users still use IE 11, and even IE10. I think it is a concern.

Nevraeka commented 8 years ago

Maybe it makes sense to list the browser support for native as we do.

I think it would be great to break down the polyfill browser support as well since more polyfills are being used now as well as versions and pieces of webcomponents.js. Breaking out the parts of webcomponents.js & webcomponents-lite.js and the support makes sense. Also taking any other polyfills and doing the same.

teppeis commented 7 years ago

Why is HTML Imports of Firefox YELLOW? Why is "IE/Edge" combined?