- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 26 Sep 2023 14:30:44 +0000
- To: public-css-archive@w3.org
> What is none of those two pseudos was generated at all? The snapshotted view would still need to be inserted into the pseudo tree (to have something visual on the screen), but since its not matched by any of the existing pseudos authors can not target it. This becomes very hard to define because we need a replaced element to show the snapshot. That said, the ambiguity with `:only-child` is a fair point. Documenting @flackr's idea about this from today's discussion. We could generate both the old/new pseudos with the following aspects: - The image for old comes from the live new snapshot. - The UA CSS sets old at `opacity: 0` and new at `opacity: 1` instead of the default cross-fade. This is conceptually what the author would do today if they wanted a direct flip to the new image. So lines up better with author's expectation? -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9406#issuecomment-1735665816 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 26 September 2023 14:30:46 UTC