+wychen who works on triggering.

This example is a bit challenging. Naively tuning the CSS property "white-space" in the viewer wouldn't work. In order to reflow the text for readability, we need to be able to distinguish the line feeds for wrapping from paragraph separators, which is not readily available in the DOM structure.

The usability view as is is not very helpful. You can give it a try by forcing this feature. Visit chrome://flags, search for reader-mode-triggering, and change it to "always". It somewhat helps by relieving you from swiping, but the formatting is pretty bad. Since we don't do well on this type of pages, I'd say the triggering logic is doing the right thing.

To correctly handle this, we might need to port the text-processing algorithm from say, fmt. I'm afraid this use case is not our top priority.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

ReaderMode folks - I haven't run into this in any other web page since them.  I'm comfortable from my side that if you think it's unimportant and want to WontFix it.

Clank Frontend triaging: Issues with an owner are by definition assigned.

If you can't work on this, please unassign yourself as owner and mark back as available or untriaged. Thanks!