- From: Theresa O'Connor via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Jul 2022 08:59:24 +0000
- To: public-css-archive@w3.org
@atanassov & I took a look at this during the TAG's F2F in London today. I think @dbaron makes a good case that this stuff isn't currently defined with enough rigor (see this issue itself, [this comment](https://github.com/whatwg/html/issues/3246#issuecomment-346475192), etc.), but also @domenic's right that pushing the maintenance burden onto ALL THE SPEC EDITORS, most of whom don't have the relevant expertise, isn't a good way to solve the problem. A (handwavy, super-high-level) possible compromise would be to write some spec text describing how this all works, but only provide one hook for other spes, for the less common case (is that the "force flushing" case?). There's a one-time operation that many folk familiar with implementations could do, namely, make a list of the things that fall into the exceptional case, and then the WG could update those specs appropriately. Going forward, people adding new features need only ask themselves, is this one of the exceptional cases, and if so, use the hook. Most of the time, they won't have to. Maybe this is something folks can consider during next week's CSS F2F. -- GitHub Notification of comment by hober Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5115#issuecomment-1196454247 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 27 July 2022 08:59:26 UTC