[csswg-drafts] Status of css-houdini-drafts and fxtf-drafts? (#13201)

LeaVerou has just created a new issue for https://github.com/w3c/csswg-drafts:

== Status of css-houdini-drafts and fxtf-drafts? ==
From https://github.com/w3c/csswg-drafts/issues/7523#issuecomment-3636220658 by @andruud: 

> But css-houdini-drafts is somewhat "deprecated" as a working arena, so I wasn't sure Async Resolution labels would be effective in that repo.

If [css-houdini-drafts](https://github.com/w3c/css-houdini-drafts) (and [fxtf-drafts](https://github.com/w3c/fxtf-drafts)) is not an active working arena, should we merge it with this repo? There are ways to do so while fully preserving commit history.

IMO either these repos should be first-class working arenas, or merged. The current state where we have _some_ issues about these specs in the css-houdini-drafts repo and some in csswg-drafts for better visibility is very suboptimal and makes it incredibly hard to track what's going on. For example `css-properties-values-api` has :
- [17 open issues here (21 total)](https://github.com/w3c/csswg-drafts/issues?q=sort%3Aupdated-desc%20is%3Aissue%20label%3Acss-properties-values-api-1)
- [26 open issues in css-houdini-drafts (91 total)](https://github.com/w3c/css-houdini-drafts/issues?q=sort%3Aupdated-desc%20is%3Aissue%20label%3Acss-properties-values-api-1)

If some specs are abandoned, we should mark them as such, same as we do for csswg-drafts specs.

cc @astearns @fantasai @tabatkins @svgeesus 

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13201 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 10 December 2025 14:02:55 UTC