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

I'm not sure if this is true but you might check to see if eval'ing the
class like that fails in a CSP environment.

On Sat, Sep 30, 2017, 10:27 PM Joe Pea <notifications@github.com> wrote:

> @robdodson <https://github.com/robdodson> that's an interesting trick. I
> did something else: I changed arrows to functions, and put the class
> definition inside an eval() and it worked that way without causing syntax
> errors.
>
> But I have another problem: Apparently this all works great with Babel's
> ES5 output, but I get errors with Buble's ES5 output (I'm using Buble to
> transpile my lib). I decided not to muck with it for now and support Edge
> 13+, and maybe by the time the lib I'm making is actually ready for
> anything serious this adapter won't be needed anymore! 😆
>
> —
> You are receiving this because you were mentioned.
>
>
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/webcomponents/issues/587#issuecomment-333354673>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABBFDdr_smTZqmKu64nKbdcp4sNsuqZoks5snyK0gaJpZM4KXuh2>
> .
>


-- 
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-333387350