4 ms·
All this effort for what is certain to be an imprecise implementation and slow (forcing the page to redo layout multiple times is not worth solving the widow pr
by hoten 5y ago
All this effort for what is certain to be an imprecise implementation and slow (forcing the page to redo layout multiple times is not worth solving the widow problem, IMO).
Why not spend the effort exploring the problem at the browser implementation level? Is there opportunity to get NYT eng time dedicated to it?
- promblom 5y agoFrom the article: > In 2013, Adobe proposed a new CSS text-wrap: balance property to make the browser do (and optimize) the heavy lifting. TextBalancer is a JavaScript implementation of this CSS property. The property has yet to be implemented into any web browsers. (Come on, guys! It’s in CSS Text Level 4.)
- hoten 5y agoYes, I read it. if they are able to make the investment they can work on the implementation themselves instead of waiting for someone else to take it up. They are the most likely to benefit from it.
- Wowfunhappy 5y ago> forcing the page to redo layout multiple times is not worth solving the widow problem, IMO I'm not sure I agree, if it enhances readability. The users are there to read articles, so this is exactly the right place to spend spare CPU cycles. Of course, it should be optimized as much as possible, and it sounds like the NYT's implementation was not very optimized. Then again, it also sounds like the NYT only briefly experimented with their version, and does not use it today. > Why not spend the effort exploring the problem at the browser implementation level? Well, but the NYT is not fundamentally a technology company, so pushing for browser changes seems beyond their scope IMO. Adobe did try, for their part.
- d2wa 5y agoAdobe has made a proposal for a new CSS attribute, but no browser has implemented it. This is discussed in the article.