author Emilio Cobos Álvarez <>
Thu, 29 Aug 2019 21:25:12 +0000
changeset 490740 49ff97acd5ce9f094430bf4538e7f32792201182
parent 422402 c9e5997437dc1802ca3d1a5bce99594870c69b15
child 497890 d933287860cb36cf5a649daef1a451f24bb216b6
permissions -rw-r--r--
Bug 1577258 - Explicitly flush layout in an a11y test. r=eeejay We have an optimization to avoid an expensive reflow from SetFullZoom, see mSuppressResizeReflow[1]. That was done because we used to do a full synchronous reflow right after. We no longer do that, but due to that member we also don't invalidate! My second patch in this bug changes the behavior of that flag so that we don't synchronously reflow, but we do invalidate. So in turn this test before the change wasn't really testing the zoomed code-path since it was using the clean layout from before the zoom operation. a11y getBounds and co. don't flush layout (they probably should), but since with my patch we dirty the frame tree, and dirty frames return bogus offsets, the test starts failing. Flush layout explicitly to ensure we're testing the zoomed code path. [1]: Differential Revision:

support-files = zoom_tree.xul

skip-if = (os == "android")
support-files = test_shadowroot_subframe.html