Bug #17107
closedmaxW for image rows is not the maximum
0%
Description
If a given maximum width for more than one image in a row is set and this imagerow is wider than the given width, that currently doesn't mean in every case that the given value really is the maximum: If there is some remainder left after dividing the maximum space for all images in a row through the number of images, the image sizes will be ceiled and an image row therefore wider than maxW.
This might result in image rows being up to 1 pixel less than the number of images in a row wider than maxW would allow the imagerow to be and may harm a layout badly - and goes the worse the more one imagerow has columns.
There is no reason for this behaviour - I'd suggest to simply substract one pixel from each image in a row as long as there is some remainder left from the division. This results in image rows normally being wider will have the exact maximum width and every single image having still about the same width with +-1 pixel.
(issue imported from #M5186)
Files