The test timeouts here are some form of bug 1141256, which causes the service
worker spawned in the parallel mode of the tests to never start up. It turns
out that avoiding sending this huge message to the mochitest logger avoids the
issue on the infrastructure, so let's re-enable these tests. Bug 1141256 still
needs to be investigated.
Switches the whole test to task based and removes most of the CPOW traffic, the
plugin checks are the notable exception.
This also makes ContentTask act sanely in the presence of tab detach by using
browser.permanentKey as the indication that the framescript has been loaded and
just listening to all frames.
Also adds a click in the upper-left of the content area to browser_tabopen_reflows.js
to make sure the mouse isn't hovered over one of the tiles causing an unexpected
reflow.
--HG--
extra : rebase_source : 2d35b13c4037721a4a76dcbc1d3090d4ab4929ea
extra : source : 49ff034c930edc2f251bb62ff794492a47e7031a
Note that this was what it was before bug 1122302 landed (which added the share
plane and this issue).
--HG--
extra : rebase_source : 16d2ae99b2cff85c4ab4c8f4f4e32a3e0cdf92e7
LayoutHelpers.getAdjustedBoxQuads now returns all quads that el.getBoxQuads returns.
The BoxModelHighlighter calculates an outer rect based on these to draw the guides.
And if the element has more than 1 quad (inline element that spans line breaks), then all quads are
highlighted.
Also all related tests were modified and a couple of new tests were added.
--HG--
extra : rebase_source : 78a7890ac547a95561ac917c1721be6ed32c5426
This test appeared to run fine under e10s, so after running 30 times
with "mochitest-browser --e10s --run-until-failure" I've re-enabled it.
--HG--
extra : rebase_source : aef9e10258f5c4c26afa2b7785bf8ed6014a5bb2
This test appeared to run fine under e10s, so after running 30 times
with "mochitest-browser --e10s --run-until-failure" I've re-enabled it.
--HG--
extra : rebase_source : 7b63db65f319cec51783349bd0597c0926549222
This test appeared to run fine under e10s, so after running 30 times
with "mochitest-browser --e10s --run-until-failure" I've re-enabled it.
--HG--
extra : rebase_source : b25e61e34d2804fb9f591d762337cd75ffa6f825
This test appeared to run fine under e10s, so after running 30 times
with "mochitest-browser --e10s --run-until-failure" I've re-enabled it.
--HG--
extra : rebase_source : 58234a0d59ae8daeabfd392a0e54fdb18246dc86
The modifications should make the test e10s compatible but I have left
it disabled as it fails due to Bug 940206.
--HG--
extra : rebase_source : 740cd8c31a57010946d9835c5ab343c38f981023
This test appeared to run fine under e10s, so after running 30 times
with "mochitest-browser --e10s --run-until-failure" I've re-enabled it.
--HG--
extra : rebase_source : 926aba196afa9e9ef8cabb235731d27752bd60d8
This test appeared to run fine under e10s, so after running 30 times
with "mochitest-browser --e10s --run-until-failure" I've re-enabled it.
--HG--
extra : rebase_source : 48b1a342709086097fa30de11ab497a83b310bdf
This test appeared to run fine under e10s, so after running 30 times
with "mochitest-browser --e10s --run-until-failure" I've re-enabled it.
--HG--
extra : rebase_source : 6d78ae747afac856de5125509b5ac36b229853bf