Re: [w3c/webcomponents] Provide a lightweight mechanism to add styles to a custom element (#468)

Then, if they're equivalent, wouldn't it be better to always implement as (2) and expose the feature to all elements? Otherwise, the performance problem it was created to mitigate is left unaddressed for built in elements, which seems like a loss given that the actual functionality provided by the feature is strictly redundant. Further, addressing this problem for built in elements later would result in API similar to if it had been designed for use with all elements in the first place (i.e. without any connection to a custom element definition), introducing a third way to do the same thing.

Do any implementors expect that (2) would result in worse performance for their implementation?

-- 
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/468#issuecomment-371378856