Font size on HTML side of Inspector was smaller than the CSS Rule View
(in Firebug theme only) Font Size for Linux was set to 80% in common.css
Font Size for Rule View was set to 11px (causing discrepancy).
Replaced font-size:80% with 11px as it was too small for easy readability
Removed font-size:11px for Rule View as it is now redundant
MozReview-Commit-ID: 4a7tY4YEHgg
For CSS files which were used via both chrome:// and resource://, I converted
all usages to resource:// and removed the chrome:// copy to reduce file
duplication.
I believe most DevTools CSS could be using resource:// throughout, but that's
left as follow up work for now.
MozReview-Commit-ID: G7oxZqjodwv
--HG--
extra : rebase_source : d6ae487f35cdeddd32aa96d95d62113ba0565b2a
The rule-view and computed-view now have tabindex="-1" on their containers
so that clicking anywhere in the views will focus them, so will tabbing
through the inspector to them.
This means that any user activity on them ends up focusing them (or any
focusable element in them, which was the case before anyway).
Because of this, pressing ctrl+F (or any other shortcut) will work correctly:
the _onShortcut callback in each of these views will detect that the active
element is the view itself and will therefore handle the event.
Note that the container element that has the tabindex attribute is a child of
the main container element that is scrollable (overflow:auto). That is
because if we use only one element for both, then grabbing the scrollbar will
focus the element and blur any field that's currently focused.
MozReview-Commit-ID: 97a1tpdlbmZ
--HG--
extra : rebase_source : 607f025a0f06064180a9cb3e72129e3c734598c6
Unmatched rules created via the "Add New Rule" button was wrongfully make other rules look not applied.
Fix returned isMatching boolean in PageStyleActor's function when the evaluated rule has multiple selectors.
Add CSS rules to make look unmatched rules' properties unmatched, like the rule's selector.
Add tests to make sur we handle unmatch rule selectors right.
MozReview-Commit-ID: FPQ7XJoa7Ba
--HG--
extra : transplant_source : %C4%F1sa%ED4%E6%8CV%8F/nK%E4%FBA%2C%A7%F5%0F
This patch was generated by the command:
find . -name "*.css" -exec sed -i -f mozpropsub {} \;
in the root of a mozilla-central tree, with the file mozpropsub
containing the contents:
s/-moz-padding-end\>/padding-inline-end/g
s/-moz-padding-start\>/padding-inline-start/g
s/-moz-margin-end\>/margin-inline-end/g
s/-moz-margin-start\>/margin-inline-start/g
s/-moz-border-end\>/border-inline-end/g
s/-moz-border-end-color\>/border-inline-end-color/g
s/-moz-border-end-style\>/border-inline-end-style/g
s/-moz-border-end-width\>/border-inline-end-width/g
s/-moz-border-start\>/border-inline-start/g
s/-moz-border-start-color\>/border-inline-start-color/g
s/-moz-border-start-style\>/border-inline-start-style/g
s/-moz-border-start-width\>/border-inline-start-width/g
While I didn't manually review all the changes, I did review the list of
files, and manually reviewed the changes in the files that I thought
were more interesting.
Note that there are a few tests that should be fixed up as well, but
I'll do that in a later patch.
MozReview-Commit-ID: EiQTuuV0MNQ
Add a negative top offset to align swatches ( color, filter, bezier, ...) with
the values they represent.
MozReview-Commit-ID: 6EIQZ2UAHuc
--HG--
extra : transplant_source : %CF%E7%86%C7%90%DB%16%9B%E9%C4E%E0W%E7%87%07%CF%C9%F4%E4
Add a swatch before angle values in the rules panel and allow cycling
through angle units with shift+click (like we already do for color units).
MozReview-Commit-ID: CWhoUQTkP1G
--HG--
extra : transplant_source : %5B%E5%AD%22%D2%20uk%07%EE%A9%E4%91YS%B3R%C3%DF%21
Kimberly Pennington
Gabriel Luong
J. Ryan Stinnett
Julian Descottes
Towkir Ahmed
Tim Nguyen
Patrick Brosset
gasolin
Jan Odvarko
Wes Kocher
Ruturaj Vartak
Nicolas Chevobbe
L. David Baron
Alexandre Poirot