- From: Ryosuke Niwa via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Jan 2020 00:17:46 +0000
- To: public-css-archive@w3.org
The order by which this flag is set is also important. It's unclear at which point relative to setting ready state, firing DOMContentLoaded or load event, this timing falls into etc... There is an issue with the second bullet point as well. "The document has pending stylesheet requests" can occur multiple times even after the document had completely finished loading by inserting a new `link` or `style` element. Should we be going back & forth between not pending on the environment & pending on the environment? Finally, the third bullet point has a reference to undefined the concept of *pending layout operations*. I don't even know what that means. Layout operations isn't a thing, is it? The third bullet point is even more problematic when we consider the prose which says "which might cause the user agent to request a font, or which depend on recently-loaded fonts". How does UA supposed to determine that? I don't think we can until we actually resolve all the computed styles. In fact, on web pages in which there is a never ending animation, UA can never determine that there is no pending task which can occur as a result of future layout changes caused by CSS / JS animations. -- GitHub Notification of comment by rniwa Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1081#issuecomment-579535283 using your GitHub account
Received on Wednesday, 29 January 2020 00:17:47 UTC