- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Apr 2022 23:26:43 +0000
- To: public-css-archive@w3.org
Summarizing the CSSWG discussion: We'd like to circle back to this after https://bugs.webkit.org/show_bug.cgi?id=235222 has gotten some more testing. If I'm understanding @Loirooriol's summary correctly, that change makes WebKit's `getComputedStyle` truthfully report the actual computed of `content`, without any "resolve-none-to-normal" magic. (Though `none` still behaves as `normal` in many situations; i.e. the used value of `none` may still be `normal`.) If that seems to be web-compatible & WebKit is able to successfully ship that change, then it seems like we should spec that behavior and change Gecko/Blink to match, to remove unnecessary magic & make `getComputedStyle` a bit closer to reporting the actual computed style (rather than the used style). -- GitHub Notification of comment by dholbert Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6503#issuecomment-1090919304 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 April 2022 23:26:45 UTC