1476812 - left:auto on a position:absolute display:inline-block element shouldn't consider floats after the inline-block that would have moved it

Status: NEW

(Core :: Layout: Positioned, defect, P3)

Description

[Thomas Wisniewski [:twisniewski]]

Attachment: test.html

In the attached test-case, Firefox pushes the red element off-screen by the width of the gray element. Other browsers place the red element's right edge along the right edge of the viewport.

Comment 1

[Emilio Cobos Álvarez (:emilio)]

Looks like there's an incremental reflow bug somewhere there. If I toggle `position` and `display` on the `.menubar` element it doesn't take effect always immediately, which looks wrong.

I don't know what we're thinking to make the width: 100% overflow the viewport somehow...

Comment 2

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

.menubar is using its hypothetical position, since it has top:auto and left:auto.  It seems reasonable that the left:auto position puts it to the right of the float, since that's where it would be if it weren't positioned.

Comment 3

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Chrome will consider the float for the hypothetical position if it comes before the inline-block, but not if it comes after.

Comment 4

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Attachment: set of four simpler tests

Comment 5

[Firefox Bug Husbandry Bot]

Migrating Webcompat whiteboard priorities to project flags. See bug 1547409.

Comment 6

[Firefox Bug Husbandry Bot]

See bug 1547409. Migrating whiteboard priority tags to program flags.

Comment 7

[Mike Taylor [:miketaylr]]

(fwiw, the site has been redesigned and the original bug is no longer break the page)

Comment 8

[Daniel Holbert [:dholbert]]

This is the root of https://github.com/webcompat/web-bugs/issues/49638 as well.

Comment 9

[Thomas Wisniewski [:twisniewski]]

Fancourier has also updated their design, and this bug no longer seems to apply there. Since we know of no other sites broken by this right now, unsetting webcompat flags.