Re: [w3c/webcomponents] Constructor arguments in custom elements (#605)

Let's close this. There are plentiful workarounds, and upon re-reading, the proposal seems to be "provide the UA with a no-argument function it can call to create elements even if the constructor takes mandatory arguments". However, I think it's much simpler and fits better with the platform to flip that around: make the constructor the no-argument function the platform calls, and if you want to have a mandatory-arguments factory, you can e.g. use static methods on your custom element class.

-- 
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/605#issuecomment-336569487