James Teh 7d0494adc2 Bug 1585851: When processing a11y insertions, don't try to move an accessible if its new previous sibling hasn't been moved into its new container yet. r=MarcoZ ... Sometimes, depending on how children were changed, children might be in the insertion list out of order; e.g. [child2, child1]. It's also possible that an earlier child (child1 in the above example) is being moved out of another container. When processing the earlier insertion (child2), we'll determine we need to move it within its parent and will fetch its new previous sibling so we can move it into the right place. However, in this case, the new previous sibling (child1) will be in the wrong container. We can't move in that case; the new previous sibling's index in parent will obviously be wrong, since it's relative to the wrong container. Therefore, we just skip the move. Since the previous sibling (child1) is later in the insertion list, the ordering will be corrected when we process that insertion. Differential Revision: https://phabricator.services.mozilla.com/D51037 --HG-- extra : moz-landing-system : lando		2019-10-30 06:32:50 +00:00
..
.eslintrc.js
448064.xhtml
471493.xhtml
884202.html
890760.html
893515.html
1072792.xhtml
1380199.html
1402999.html
1415667.html
1463962.html
1484778.html
1494707.html
1503964.html
1572811.html
1578282.html
1585851.html	Bug 1585851: When processing a11y insertions, don't try to move an accessible if its new previous sibling hasn't been moved into its new container yet. r=MarcoZ	2019-10-30 06:32:50 +00:00
crashtests.list	Bug 1585851: When processing a11y insertions, don't try to move an accessible if its new previous sibling hasn't been moved into its new container yet. r=MarcoZ	2019-10-30 06:32:50 +00:00
last_test_to_unload_testsuite.xhtml