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

Again, I can't emphasize enough our objection for using a new cascading order.

This feature was originally proposed as a way of avoiding the performance penalty to have a shadow root. Introducing a new cascading order would totally defeat that performance benefit by introducing more complexity and performance cost in our implementation.

In general, this issue has morphed into a feature which lacks a clear list of use cases and instead of a solution looking for use cases to back that up. We need to re-enumerate a clear list of *concrete* use cases this feature is supposed to address since the proposed solution and the original problem make no sense whatsoever at this point.

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