- From: Gwern Branwen via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Apr 2024 20:24:45 +0000
- To: public-css-archive@w3.org
I didn't say the current Chrome implementation of `pretty` had *failed* - just that it was opinionated, and we had other opinions. (You and the Chrome dev Ishii perhaps have more tolerance of spacing and more dislike of hyphens than we do, and there's no arguing taste there; but we've been burned by some extremely bad looking lines on mobile when line-stretching happens, so we worry about it a lot, while hyphens are so ordinary as to not be a big deal or worth incurring costs like stretched lines to minimize.) But if a lot of the instances aren't clearly better even by your assessment, you can see why we wouldn't be too eager to go out of our way to add & debug fairly exotic new CSS to opt into this brand new, possibly buggy, non-standardized-cross-browser, opinionated package of changes, when there's just one part we are sure we want. And so I am simply mentioning, in the context of the discussion of whether to add knobs, that we *would* like a knob for that part, and would not like to have use `pretty` as a take-it-or-leave-it deal, because as it stands now - we would have to leave it. -- GitHub Notification of comment by gwern Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3473#issuecomment-2033028973 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 2 April 2024 20:24:46 UTC