Bugzilla

(In reply to Daniel Holbert [:dholbert] from comment #14)
> The element here (circled in red in comment 12) seems to be a sticky-positioned element, and it's got a different visual-stacking-order in Firefox vs. Chrome. 

Actually the more relevant element is an ancestor which is absolutely positioned, not this sticky-positioned one.

Its containing block happens to be `display:inline` from this rule:
```
.css-376mun {
  position: relative;
  display: inline;
}
```
And that makes Gecko/WebKit disagree with Chromium about the stacking order for its abspos descendants vs. later in-flow descendants, as shown in this attached testcase.

In this testcase, Gecko and WebKit render the blue div in front, whereas Chromium renders the orange div in front.

(In reply to Daniel Holbert [:dholbert] from comment #14)
> The element here (circled in red in comment 12) seems to be a sticky-positioned element, and it's got a different visual-stacking-order in Firefox vs. Chrome. 

Actually the more relevant element is an ancestor which is absolutely positioned, not this sticky-positioned one.

Its containing block happens to be `display:inline` from this rule:
```css
.css-376mun {
  position: relative;
  display: inline;
}
```
And that makes Gecko/WebKit disagree with Chromium about the stacking order for its abspos descendants vs. later in-flow descendants, as shown in this attached testcase.

In this testcase, Gecko and WebKit render the blue div in front, whereas Chromium renders the orange div in front.