зеркало из https://github.com/mozilla/gecko-dev.git
da97c00bb1
Instead, sort stuff using CSSOrderAwareFrameIterator. The current sorting is broken in presence of dynamic insertions, consider the following <Child(order)> combination in the DOM: <A(1000)> <B(0)> That'd look like: <B(0)> <A(1000)> On the frame tree. However when appending a child before B so that the DOM looks like: <A(1000)> <C(0)> <B(0)> The frame constructor will properly insert after A, and the reordering, which is stable, will end up with: <B(0)> <C(0)> <A(1000)> Which is the wrong frame tree order. We only use -moz-box-ordinal-group in regular sprocket layout, so just handle it there rather than everywhere. Similarly, we only rely on it for in-flow stuff, so remove the test for that added in bug 877890 (flex changed behavior afterwards, interestingly enough). Differential Revision: https://phabricator.services.mozilla.com/D94790 |
||
|---|---|---|
| .. | ||
| dynamic-1-add-to-one-grouped.xhtml | ||
| dynamic-1-add-to-two-grouped-1.xhtml | ||
| dynamic-1-add-to-two-grouped-2.xhtml | ||
| dynamic-1-ref.xhtml | ||
| dynamic-1-remove-to-none-grouped.xhtml | ||
| dynamic-1-remove-to-one-grouped-1.xhtml | ||
| dynamic-1-remove-to-one-grouped-2.xhtml | ||
| reftest.list | ||