I'm not sure what the underlying mechanics are, but from (informally) comparing sites that work/don't with reader view, it seems that they have a heuristic like "look for the element with the most text," and display that to the exclusion of all others. The developer effort spent making SE's design accessible could be partially directed toward making SE compatible with standard tools.ĭiscussion: Every browser implements "reader view" differently, but most reader views nail the majority of "article" style sites, while nearly all fail on SO/SE posts. This means users cannot rely on reader view for SE sites. Relation to recent change in post formatting (line-spacing, background-color): This is neither for nor against the New post formatting, but it is related in that when you tap the native "reader view" in a browser,* often all that's readable is the question or the first answer the other content simply isn't there. Since it is impossible for a fixed design to equally accommodate all users, I propose investigating whether the HTML structure of SE pages could be modified to play nicely with browser reader views.Įdit: I opened a question on StackOverflow exploring the technical reasons/solutions for this incompatibility. Tl dr: SE pages break almost all browser "reader modes." Reader mode is designed to allow users to customize the appearance and formatting of a web page to meet their reading needs.
0 Comments
Leave a Reply. |