Re: [w3c/webcomponents] Non-class based example of customElement.define() (#587)

In case this is helpful, we are detecting the browser and dynamically
loading the right libraries based on the browser.  We do it inside our
library so our users don't have to see that.

But instead of rolling your own dynamic loading, you could instead use
https://github.com/webcomponents/webcomponentsjs#webcomponents-loaderjs.
This does dynamic loading for you.

Best,
Jeff Robbins

On Sat, Sep 30, 2017 at 3:01 PM Joe Pea <notifications@github.com> wrote:

> What will this do in older browsers that have a window.customElements
> polyfill? Hmmm, also class syntax will trip IE11.
>
> What's your recommendation for libs then? I don't want to tell people:
> "detect browser on server side and send the script tag if needed" for
> example. I want to tell people, regardless of browser, "use this script tag
> for my library" and done.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/webcomponents/issues/587#issuecomment-333328992>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ACAWh_k8NlA5nTzLyJyxZf7QbZgUq1rLks5sno_zgaJpZM4KXuh2>
> .
>


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/587#issuecomment-333330805