- From: Mason Freed via GitHub <sysbot+gh@w3.org>
- Date: Mon, 31 Mar 2025 21:19:44 +0000
- To: public-css-archive@w3.org
> > I guess I'm curious what you had in mind in terms of implementing these? It sounds like it would make the cascaded value of display dependent on the cascaded value of auto, and properties can't really depend on each other like that. > > WebKit has a step in the StyleAdjuster that can adjust styles based on the `appearance` value. Chrome has a method at least to adjust styles based on `appearance: base` so I imagine it's not impossible to make it happen for `auto` or `none`. Right - we had to solve this problem for customizable-`<select>`. See, e.g., all of the UA rules that have `-internal-auto-base()`, such as [this one](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/html/resources/html.css;l=1717;drc=5fc3d3c782eff9f50ab9a20644faf49b339506f8). It should be possible to modify that to account for `none` also. -- GitHub Notification of comment by mfreed7 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11845#issuecomment-2767424522 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 31 March 2025 21:19:45 UTC