1533151 - Gecko and Blink disagree on where to place abs.pos. children of fragmented inline CB

Status: RESOLVED WORKSFORME

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

Description

[Thomas Wisniewski [:twisniewski]]

Attachment: test.html

I left this testcase as-is, as I'm unsure if there are multiple aspects that Gecko and Blink disagree on.

Visually, Blink seems to not push the "X" outside of its containing block despite it having a left:-56px, while Firefox does. However, based on the complexity of the case I can't be sure if that's really what's going on.

This is affecting omnitv's site, as reported in https://webcompat.com/issues/26636

Comment 1

[Emilio Cobos Álvarez (:emilio)]

We're inconsistent here, you can coerce Gecko to render right toggling the left property a couple times, and also toggling the content property on the pseudo-element. This has relatively positioned inlines, so it seems likely that this bug is similar to the bugs dependent on bug 255139.

Comment 2

[Mats Palmgren (inactive)]

Attachment: Testcase #2 (simplified version of the first testcase)

Comment 3

[Mats Palmgren (inactive)]

This seems more like bug 489100 to me. See also bug 1158666.
(the "fragmentation" in this case is due to the ib-split)

Comment 4

[Sean Voisen (:svoisen)]

Bulk moving bugs that have been triaged P4 to P3 (P4 is reserved for WPT bugs).

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

[Dennis Schubert [:denschub]]

From the testcases and the live site reported, I can see that the site is still broken in Firefox - but it's also now broken in Chrome the same way. Possible that they changed their behavior here, so I'll close this bug.