- From: vmpstr via GitHub <sysbot+gh@w3.org>
- Date: Fri, 14 Oct 2022 14:48:52 +0000
- To: public-css-archive@w3.org
> t's simpler to treat these pseudo-elements like any other element where from the developer's perspective, the style is always up to date once the `ready` promise resolves and they are accessible in script. To be pedantic here, there are two notions here: the script is up to date as specified in the UA stylesheet, and when that UA stylesheet is updated to reflect a changed source element. I agree that script should always observe values in the UA stylesheet when they getComputedStyle, and that something that already happens for all elements. However, when the stylesheet is updated to represent the changed source element does not have a precedent, so treating this as we would in any other element doesn't mean much. I think you're suggesting updating the UA stylesheet whenever script requests getComputedStyle, but I suspect that complicates the implementation quite a bit. I would still prefer to have an explicit step with specified timing that takes the changed source element values and updates the UA stylesheet -- GitHub Notification of comment by vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7812#issuecomment-1279111270 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 14 October 2022 14:48:54 UTC