lang-css autocomplete is outdated #1696

Open
opened 2026-04-20 13:54:23 +02:00 by LeoMcA · 1 comment

We've noticed that the https://code.haverbeke.berlin/codemirror/lang-css/src/branch/main/src/complete.ts hard-coded list of autocomplete values for CSS is getting outdated. One example of this is container-type which doesn't list inline-size nor size.

We've had some ideas around how we could fix this downstream using data from webref here: https://github.com/mdn/fred/issues/1482

But could this be fixed upstream instead?

We've noticed that the https://code.haverbeke.berlin/codemirror/lang-css/src/branch/main/src/complete.ts hard-coded list of autocomplete values for CSS is getting outdated. One example of this is `container-type` which doesn't list `inline-size` nor `size`. We've had some ideas around how we could fix this downstream using data from [webref](https://github.com/w3c/webref) here: https://github.com/mdn/fred/issues/1482 But could this be fixed upstream instead?
Owner

A possible complication is that I'm not interested in including stuff that's not widely implemented, and at this point the CSS spec feels like a spawling mess, part of which isn't, as far as I'm aware, likely to be implemented soon. I don't want to weigh down this file with every possible property found in some draft. So I've been resisting just throwing all of webref in there.

Ideally we'd have some metrics about actual use. I guess caniuse.com might provide browser support information, at least. If you find some way to filter the properties (and value names, etc) down to something that provides practical modern completion without adding too much noise or making this file gigantic, I'd be interested in a PR.

A possible complication is that I'm not interested in including stuff that's not widely implemented, and at this point the CSS spec feels like a spawling mess, part of which isn't, as far as I'm aware, likely to be implemented soon. I don't want to weigh down this file with every possible property found in some draft. So I've been resisting just throwing all of webref in there. Ideally we'd have some metrics about actual use. I guess caniuse.com might provide browser support information, at least. If you find some way to filter the properties (and value names, etc) down to something that provides practical modern completion without adding too much noise or making this file gigantic, I'd be interested in a PR.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
codemirror/dev#1696
No description provided.