@janbrasna Do you remember what the problem is with white-space?

@stephaniehobson So the issue is what risk this might pose for downstream consumers, where balancing text IIUC actually competes with white-space property per se (as one is asking for no wrapping and the other is asking for balanced wrapping) — guess I wanted to check a few layouts over at kitsune, fxa, relay et al. how such a change wholesale could interfere with what they have added to the cascade in addition to protocol styling.

(For just bedrock this should be a non-issue, as balancing headings has been around for some time now.)

Seems like it follows the cascade in Firefox and Chrome so any custom styles they have applied should take president if they're importing their styles after the Protocol one.

I think we're safe to go ahead but I'd add something to the CHANGELOG's migration notes to search for any place where white-space: nowrap is defined and make sure it has a higher specificity.

It might be a nice change to include with V20 which will have other font updates.

@janbrasna Do you want to add some CHANGELOG notes to this PR so I can merge it? I'm thinking V20 will go sometime next week and I'd like to have this in it.

@stephaniehobson Yup, on it. I'll try to add some reasonable heads up to the migration notes too.

(I haven't checked this is not also included in the wholesale font update in the other PR, porting other related values battle tested in bedrock, but will do so! — I actually found this to be a solution to an "unrelated" whitespace / hyphens / wordwrapping issue where having balanced headings helps avoiding a regression when allowing implicit hyphens, so can't wait to have this in and start removing weird forced word wrapping.)

Landing this in a major / breaking release makes the most sense; I was mainly cautious about slipping this in a minor update regarding any impact to consumers, but v20 is great to have this included in, being full of similar changes. 🚀