Sigh, the CSSWG decided today *not* to change "nowrap" to "no-wrap", enshrining the confusing spelling forever.
5
3
3
@tabatkins If you disagree with this, please email www-style@w3.org about this, so the rest of the WG actually knows people don't like this.
1
3
1
@tabatkins That's unfair. You didn't say why. One argument was script now has to check for 2 values, not 1. Not worth it for a hyphen glitch
1
1
@fantasai Yeah, Twitter has length limits, and I'm frustrated. But I think this is status quo fallacy; script stuff isn't as bad as spelling
1
@fantasai ("nowrap" gets written in stylesheets *way* more than it gets written in scripts, easy to verify with a github search)
1
@tabatkins Parsing it in as a *specified* value of 'nowrap' would solve that problem without affecting DOM, but you didn't like that option.
3
@fantasai But seriously, parsing-level isn't doable. It means "a { --foo: no-wrap; white-space: var(--foo); }" doesn't work.
1
