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
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 : cfe40b90c62c0973e5636bf0ffc80a166aaeb26e
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 : 017320c455827107d4137b0e5003a3d2d66f08b0
This test appeared to run fine under e10s. The reason for disabling
originally was an error[1] that no longer appears to occur. running
30 times with "mochitest-browser --e10s --run-until-failure" did not
result in any errors.
[1] MockFilePicker cleanup failing ( nsresult: "0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED)" location: "JS frame :: resource://specialpowers/MockFilePicker.jsm :: this.MockFilePicker.cleanup :: line 84")
--HG--
extra : rebase_source : ac689422859bab56af2fa176f80312db3a4f110d
This test appeared to run fine under e10s. The reason for disabling
originally was an error[1] that no longer appears to occur.
[1] MockFilePicker cleanup failing ( nsresult: "0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED)" location: "JS frame :: resource://specialpowers/MockFilePicker.jsm :: this.MockFilePicker.cleanup :: line 84")
--HG--
extra : rebase_source : 77144460bea809c3969bd99ed583014f4728936d
Factor some of the repeated ContentTask.spawns into their own functions
and comment what's happening a bit better. A few variables are also
renamed to clarify what they represent.
--HG--
extra : rebase_source : ececaa41c48138f03114f1a017889bd7804aaf14
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 : a2f486a5f10bf7e3b9687fe8685a0a35dbb26d44
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 : ff82148650f54bc66cccd08abae9c10cba9f2bed
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 : 255322b4277cd045d7f8556b7f98c7d78320961b
The new version which is e10s compatible has been completely disabled
though because of leaks in non-e10s test runs (see Bug 1142678).
The old non-e10s compatible test has been renamed to
browser_privatebrowsing_aboutHomeButtonAfterWindowClose_old.js and is
still enabled until Bug 1142678 is fixed to maintain the test coverage.
--HG--
extra : rebase_source : 197c25b2f89909735b02c2d366d6aca911993449
