The `clear` property currently only applies to block-Level elements, not to floats, regions, or pages, because the related CSS Page Floats Module (https://www.w3.org/TR/css-page-floats-3/) is not implemented yet.
For the same reason, we don't check `float-offset` and `float-defer` at the moment.
Differential Revision: https://phabricator.services.mozilla.com/D215299
This is done to avoid a performance issue with deeply nested rules,
where computing the desugared selector can be super expensive.
This should help overall since we're doing a bit less work, as well
as returning smaller data.
Differential Revision: https://phabricator.services.mozilla.com/D207727
test_css-logic-media-queries.html was only checking this property,
and we have a mochitest equivalent checking the UI (browser_rules_media-queries.js),
so we remove it.
Depends on D193872
Differential Revision: https://phabricator.services.mozilla.com/D193873
Given that we get the rules from `InspectorUtils.getCSSStyleRules`, the selectors
are already sorted the way the platform handles them.
We only need to reorder those in case a value is important, otherwise we rely
on the original rules order.
Extensive tests are added to make sure we covered possible cases.
Differential Revision: https://phabricator.services.mozilla.com/D182780
Given that we get the rules from `InspectorUtils.getCSSStyleRules`, the selectors
are already sorted the way the platform handles them.
We only need to reorder those in case a value is important, otherwise we rely
on the original rules order.
Extensive tests are added to make sure we covered possible cases.
Differential Revision: https://phabricator.services.mozilla.com/D182780
Subtle things:
* We now have shadow trees in NAC, inception! Only a couple lines of
code in the style system had to be changed to match :host rules and
so properly.
* Had to make highlighters.css contentaccessible, because otherwise we
can't load it from the shadow tree. I don't think it's a big deal.
* I removed some of the code from highlighters.css that claimed that
stuff inherited from the html element. That's just no longer true.
* Had to switch from `setAttribute("style", ...)` to `.style = ...;`.
This is needed because CSSOM from chrome code bypasses CSP (as
AnonymousContent did), but setAttribute() doesn't, see bug 1424474.
Differential Revision: https://phabricator.services.mozilla.com/D173998
Subtle things:
* We now have shadow trees in NAC, inception! Only a couple lines of
code in the style system had to be changed to match :host rules and
so properly.
* Had to make highlighters.css contentaccessible, because otherwise we
can't load it from the shadow tree. I don't think it's a big deal.
* I removed some of the code from highlighters.css that claimed that
stuff inherited from the html element. That's just no longer true.
* Had to switch from `setAttribute("style", ...)` to `.style = ...;`.
This is needed because CSSOM from chrome code bypasses CSP (as
AnonymousContent did), but setAttribute() doesn't, see bug 1424474.
Differential Revision: https://phabricator.services.mozilla.com/D173998
Subtle things:
* We now have shadow trees in NAC, inception! Only a couple lines of
code in the style system had to be changed to match :host rules and
so properly.
* Had to make highlighters.css contentaccessible, because otherwise we
can't load it from the shadow tree. I don't think it's a big deal.
* I removed some of the code from highlighters.css that claimed that
stuff inherited from the html element. That's just no longer true.
* Had to switch from `setAttribute("style", ...)` to `.style = ...;`.
This is needed because CSSOM from chrome code bypasses CSP (as
AnonymousContent did), but setAttribute() doesn't, see bug 1424474.
Differential Revision: https://phabricator.services.mozilla.com/D173998
Return the desugared selectors from `getMatchedSelectors`, and use the desugared
selector we have on the rule to match against those.
A test case with nested rule is added to ensure the issue is properly fixed.
Differential Revision: https://phabricator.services.mozilla.com/D181773
This removes the devtools.target-switching.server.enabled preference,
which was only having an impact on tab debugging.
Toolboxes other than tabs aren't yet using "server side target switching",
which will probably happen once we enable EFT in these and
we would probably not use a preference for enabling this.
This remove all assertions in tests covering client side target switching.
And it removed a couple of tests that became irrelevant.
Differential Revision: https://phabricator.services.mozilla.com/D166921