- From: robglidden <notifications@github.com>
- Date: Mon, 04 Mar 2024 16:10:34 -0800
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 5 March 2024 00:10:38 UTC
@sorvell Indeed, nested declarative shadow trees is I where I am finding particular benefit to "inheriting" shadow @layers. Even a typical `<header-container>` with a `<nav-bar>` inside it, a shadow tree in a shadow tree similar to what you describe. If I want the `<nav-bar>` to have a `<button>` inside, I may want the button style to reset from even a [simple reset layer](https://piccalil.li/blog/a-more-modern-css-reset/), a page button style or a `<nav-bar>` button style. Please understand I am only using the term "inherit" because it is an available CSS-wide keyword reserved-for-future use @layer name. But in the case you describe, "inheritance" - like regular old CSS inheritance that sets some CSS properties not set by the cascade - seems like an apt term. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/909#issuecomment-1977706818 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/909/1977706818@github.com>
Received on Tuesday, 5 March 2024 00:10:38 UTC