> 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 th

> 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.