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

I too really want to see this through. As others have said, the [ElementCreationOptions](https://dom.spec.whatwg.org/#dictdef-elementcreationoptions) dictionary already exists and may be extended as the requirements change.

In regards to DI-patterns, following @domenic's suggestion of providing default constructor arguments directly from the element constructor means that the Custom Element classes must depend on the service container, which, besides being a bit verbose and slightly annoying in practice, also may lead to circular dependencies (depending on the implementation) if the Custom Element itself is also injected as a service.

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