Fixed width rendering is ridiculous

[werner_daehn]

This is how the new blog posts look like on a 4k display. (click on the images and pretend your monitor is large enough to show the entire image at once)

Lots of white space left and right, images are too small to see. Okay, I can set the zoom factor to 400% to get the full width being used, but is that so much better?

In contrast, this is how a Wikipedia page renders

There are two flawed assumptions here:

1. The assumption that 672px width is a common display width. That was true 20 years ago.

2. The assumption that all displays are similar size. Which is totally wrong. We have display width from 1024 to 4096 pixel or larger. The dpi are different as well, it could be a 2k monitor with 40" or a 4k tablet with 8".

HTML takes care of all of that, yet it is actively prevented by forcing a fixed width.

The solution would be simple:

1. No absolute width but percent.

2. In the editor a tag to start a new paragraph to avoid images being out of sync with the text, e.g. a long paragraph with a right hand image should be rendered as one paragraph. The next paragraph should start below the image. Just like Wikipedia does as well.

3. Optionally show differently sized images. On a large screen the original image, on smaller screens the resized version, responsive design: <img srcset="image-b.jpg" src="image-a.jpg" alt="an image" />

[tamira · Accepted solution]

Hi Werner,

The width of the blog post was reduced for some reason and that is a bug I can confirm. In general the content is as wide as a comment (960 px as far as I remember).

That already helps a bit. Personally I do agree that the amount of whitespace should be reduced and the feedback that you and other community members give about this proves the need to improve, therefore we raised this to our user experience team to consider and are now waiting for an answer.

Thanks and regards,

Gabi