- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Jul 2018 20:22:06 +0000
- To: public-css-archive@w3.org
Oh yeah, actual line-breaking *within* the boxes is an unrelated thing we don't have to worry about. > Given that neither of these calculations have crisp, clear algorithms for finding the optimal solution, I'd be hesitant about baking a full algorithm into the spec. If we bake an algo into the spec, and later find a more optimal version that gives slightly different results, we can either decide the compat isn't bad and update the spec, or decide the compat is too bad and stick with our old algo. If we don't bake an algo into the spec, implementations will still choose some algorithm for now. If they later find a more optimal version, they'll also either decide they can or can't update, based on compat pain. So the two situations are identical here, and there's no existing platform compat or similar UA-varying constraints making it more attractive to leave it up to quality-of-implementation, so there's no reason to *not* specify an algorithm. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2949#issuecomment-408223317 using your GitHub account
Received on Thursday, 26 July 2018 20:22:09 UTC