It's just as easy to directly set the preprocessor macro in the moz.build
files. Using this variable doesn't really buy us anything.
This patch also removes unused code from rdf/tests/dsds.
1) ./mach marionette-webapi <dir>/
- selects all test cases under <dir> and execute them only in
in-process mode.
2) ./mach marionette-webapi --type=+oop <dir>/
- selects all test cases under <dir> and execute them only in oop
mode.
3) ./mach marionette-webapi --type=-oop <dir>/
- selects all test cases under <dir> and execute them only in
in-process mode.
4) ./mach marionette-webapi <test>
- execute <test> only in in-process mode.
5) ./mach marionette-webapi --type=+oop <test>
- execute <test> only in oop mode.
6) ./mach marionette-webapi --type=-oop <test>
- execute <test> only in in-process mode.
7) ./mach marionette-webapi <dir>/manifest.ini
- selects all active test cases listed in <dir>/manifest.ini and
execute them in the mode(s) according to the manifest.
8) ./mach marionette-webapi --type=+oop <dir>/manifest.ini
- selects all active, oop={true,both} test cases listed in
<dir>/manifest.ini and execute them only in oop mode.
9) ./mach marionette-webapi --type=-oop <dir>/manifest.ini
- selects all active, oop={false,both} test cases listed in
<dir>/manifest.ini and execute them only in in-process mode.
This was a regression from bug 133165 which I noticed while working on
bug 480888, but wished to fix in a separate patch (despite that it would
have been slightly easier to fix it in the same patch).
The outline-overflow-inline-block-* tests fail, as expected, with the
aOverflowOverride parameter to UnionBorderBoxes always changed to null.
Note that the outline-overflow-inline-block-* tests depend on the fix
for bug 709014.
Prior to this patch, we failed to honor:
* margin-left on elements in inline layout with 0 width and 0 height
* margin-right on elements in inline layout with 0 width
I think that was because the code in CanPlaceFrame to discard both
margins when the width was 0 was running after the left-margin was
applied, unless the later code in PlaceFrame (checking both width 0 and
height 0) un-applied that left margin.
The assertion count change in test_value_computation.html is due to 2
additional "bad width" assertions (I presume from honoring large
margins that were previously ignored).
The change to 538935-1-ref.html is to match an improvement in rendering
of the margins in the test, where both sides of the margin are now
honored.
The change to layout/reftests/text-overflow/marker-basic-ref.html is to
keep the reference (which uses margins) rendering the same way following
the changes to margin handling.
The new behavior (in the reftests added in layout/reftests/inline/)
matches at least Chromium; I didn't check any other browsers.
This guarantees that the animated geometry root for an item is always in the
same display list coordinate system as the frame.
--HG--
extra : rebase_source : 249fd847a2c08f8d0846d698cce9dd4681e38a98
