Bugzilla

Looks like our behavior here changed twice.

When this bug was filed, each image forced itself to have a container with the image's intrinsic width (700px).

Then we changed (for the better) in this commit range, I suspect due to bug 1909761:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=e8cf043939ae46485e1f683456c399b124b688cd&tochange=7fa1ed101e2409de766a42d4f784acfb45a95fa2

In builds immediately after that^ fix range, there's still blank space between the images, but that space squishes to fit the available space (based on the viewport size).

Then we changed again in this commit range, due to bug 1926015:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=a4434b7aabdac9a19413cbeff360c874bb138110&tochange=7df628ab162c87151d7783027905fa7950da76ef

After that point, we match Chrome on the testcase and don't show any space between the images here.

--> Seems to have been fixed by bug  1926015.

Looks like our behavior here changed twice.

When this bug was filed, each image forced itself to have a container with the image's intrinsic width (700px).

Then we changed (for the better) in this commit range, I suspect due to bug 1909761:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=e8cf043939ae46485e1f683456c399b124b688cd&tochange=7fa1ed101e2409de766a42d4f784acfb45a95fa2

In builds immediately after that^ fix range, there's still blank space between the images, but that space squishes to fit the available space (based on the viewport size).  But if your viewport is sufficiently large, then the images reserve 700px of horizontal space.

Then we changed again in this commit range, due to bug 1926015:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=a4434b7aabdac9a19413cbeff360c874bb138110&tochange=7df628ab162c87151d7783027905fa7950da76ef

After that point, we match Chrome on the testcase and don't show any space between the images here.

--> Seems to have been fixed by bug  1926015.