I'm using FF on linux, and my browser occupies the left half of my screen.
The first, top image is what that tab looked like when it was initially rendered. Everything jumbled on top of everything else. Maybe that's partly or totally FF's "fault", but it is where the page is going to be rendered for a significant portion of people, and it is what it is, despite what the page designer wishes.
The second image is the browser in full screen mode. Everything readable. Big left and right whitespace columns, which is fine. In fact if the text stretched across the whole page that would have been its own readability problem.
Notice the code sample, rendered in a box. There's a significant amount of whitespace on the right of the box, making the box wider than necessary. Notice the article text seems to take the width of the box. I don't know enough about the front end to want to figure whether that's the case, or if the text and box are taking the width of some more encompassing element.
Either way, the third image is the browser un-fullscreened. Somehow the act of fullscreening and un-fullscreening made the page render sensibly. Yay.
But now the text is cut off on the right. The text is flowing according to some element or directive that ignores browser width. I hate this, particularly because it's so unnecessary.
The fourth, final image is that page, rendered when the browser has styles turned off. It's so 90s! It's so readable! It also shows that it can be done.
Had the page been designed with all its beautiful design elements (and they are beautiful), but rendered more to the browser than to some static design idea, we all would have been spared this rant, and I would be finished reading the article by this time.
My screenshots of this page:
http://imgur.com/a/v0Wmf
I'm using FF on linux, and my browser occupies the left half of my screen.
The first, top image is what that tab looked like when it was initially rendered. Everything jumbled on top of everything else. Maybe that's partly or totally FF's "fault", but it is where the page is going to be rendered for a significant portion of people, and it is what it is, despite what the page designer wishes.
The second image is the browser in full screen mode. Everything readable. Big left and right whitespace columns, which is fine. In fact if the text stretched across the whole page that would have been its own readability problem.
Notice the code sample, rendered in a box. There's a significant amount of whitespace on the right of the box, making the box wider than necessary. Notice the article text seems to take the width of the box. I don't know enough about the front end to want to figure whether that's the case, or if the text and box are taking the width of some more encompassing element.
Either way, the third image is the browser un-fullscreened. Somehow the act of fullscreening and un-fullscreening made the page render sensibly. Yay.
But now the text is cut off on the right. The text is flowing according to some element or directive that ignores browser width. I hate this, particularly because it's so unnecessary.
The fourth, final image is that page, rendered when the browser has styles turned off. It's so 90s! It's so readable! It also shows that it can be done.
Had the page been designed with all its beautiful design elements (and they are beautiful), but rendered more to the browser than to some static design idea, we all would have been spared this rant, and I would be finished reading the article by this time.
Won't you help?