- From: Simon Pieters via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Jun 2023 19:10:02 +0000
- To: public-css-archive@w3.org
> My point continues to be that "behavior defined by text in the CSS spec" and "behavior defined by text in a UA stylesheet (in a CSS spec)" are functionally identical, and drawing a distinction between them for siloing reasons doesn't make sense. Sure. I guess the distinction I care about is whether it's a monkey patch of HTML that should be upstreamed when sufficiently stable, or is part of the CSS language. > Either the behavior is implemented and testable or it's not; trying to say that an HTML test that exercises the area must fail because the now-implemented behavior is specified somewhere else (whether as a stylesheet or in prose) doesn't make a lot of sense. Sometimes things are just interlocked. If a spec with monkey patches is still experimental (any spec, not just for CSS) I think it's generally premature to change the "upstream" tests. But also, as far as I know this hasn't happened to date, rendering tests in `html/` just test what's in the HTML spec. -- GitHub Notification of comment by zcorpan Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8959#issuecomment-1597635860 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 19 June 2023 19:10:03 UTC