Here we make updates on reflow slower (with a throttle) cause we don't
really need to update live.
We also filter all reflows that do not cause either the list of grids or
the current outline to change.
Finally, we also attach NodeActors to GridActor forms (when they are know)
in order to avoid one more round-trip to the server.
Globally, this makes performance of the grid panel far better on pages that
cause many reflows.
Note that this commit also fixes a debounce vs. throttle confusion that
existed in an inspector utils file. The throttle function there was actually
a debounce function, so it was renamed, and an actual throttle function
was added.
MozReview-Commit-ID: GeqgZR0o0E6
--HG--
extra : rebase_source : 6b9719379dcbd4479bded26014aa3742bd75208e
Here we make updates on reflow slower (with a throttle) cause we don't
really need to update live.
We also filter all reflows that do not cause either the list of grids or
the current outline to change.
Finally, we also attach NodeActors to GridActor forms (when they are know)
in order to avoid one more round-trip to the server.
Globally, this makes performance of the grid panel far better on pages that
cause many reflows.
Note that this commit also fixes a debounce vs. throttle confusion that
existed in an inspector utils file. The throttle function there was actually
a debounce function, so it was renamed, and an actual throttle function
was added.
MozReview-Commit-ID: GeqgZR0o0E6
--HG--
extra : rebase_source : a2792a0ec4cad2034965d36648f0675ae4f52d86
Changes to Promise tests designed to test .then(null) have been reverted, and the browser/extensions directory was excluded because the projects it contains have a separate process for accepting changes.
MozReview-Commit-ID: 1buqgX1EP4P
--HG--
extra : rebase_source : 3a9ea310d3e4a8642aabbc10636c04bfe2e77070
The legacy performance path supports servers running Firefox 42 and earlier.
Now that Firefox OS is no longer supported, there's no reason to keep this
around.
MozReview-Commit-ID: K40e93VUjj9
--HG--
extra : rebase_source : ec2fbe68b7fe2f4d8e53b30d194dc026294b5f53
This changes the behavior of the element picker so that when it is
cancelled the previously selected DOM node is re-scrolled into view.
Additionally the existing behavior of the keyboard shortcuts for the
element picker was broken when the devtools toolbox was docked. The main
content area was not being focused, so the keyboard shortcuts for the
element picker were not being used. When the toolbox is detached, the
focus event is still not fired, as it's not desirable to have the
content pop into view over the devtools.
Finally there is now an additional implementation of the Escape shortcut
when the devtools are focused. The console Escape shortcut is ignored
until the element picker has been disabled making disabling the element
picker consistent irrelevant of the context.
MozReview-Commit-ID: HxENmPBoTcD
--HG--
extra : rebase_source : 067b51d4c7324f2e59fc698dbd5bb01ad2b29205
This caching feature is no longer valid as the client-side database
will not necessarily be the same as the server since the DB is
only built on nightly.
MozReview-Commit-ID: 550EQmgO9O7
--HG--
extra : rebase_source : 8863a9b42a976c5b6a6b8d4a8e2481b50f2ffa86
This caching feature is no longer valid as the client-side database
will not necessarily be the same as the server since the DB is
only built on nightly.
MozReview-Commit-ID: 550EQmgO9O7
--HG--
extra : rebase_source : 9d924ea3a4c33995ab5db1e854404f4f181ecd41
In preparation for the additional files in the `mach generate-css-db`
command, collect the CSS files into a folder.
MozReview-Commit-ID: 9JRVsC2NMK8
--HG--
rename : devtools/shared/css-color-db.js => devtools/shared/css/color-db.js
rename : devtools/shared/css-lexer.js => devtools/shared/css/lexer.js
rename : devtools/shared/css-properties-db.js => devtools/shared/css/properties-db.js
extra : rebase_source : b73bbe7fcf8177a25b41ecdd6d6c760ed1472fb7
This creates an easy interface for getting the static css database, and
splits up the initCssProperties function into smaller re-usable parts.
MozReview-Commit-ID: G86bNy3KQDp
--HG--
extra : rebase_source : 608df38114de31320594516ca776cc35ddb6ee8e
I explicitly did not migrate the localizations of the external properties file brand.properties.
This should be handled as part of Bug 1297733.
MozReview-Commit-ID: JXomOmr37xV
--HG--
extra : rebase_source : 0a4e25ba76748e159e389a7b6d42f6cf82d412aa
extra : intermediate-source : 44b1e19c5f2fc03d54ecba9507c30df4caff343f
extra : source : 2eee0a90aa25cae44f5bd1fb5c4d60438a6ceb54
The eyedropper can be shown in 2 distinct ways:
- the 'eyedropper' gcli command can be called (from the dev toolboar
or from the browser devtools menu),
- or the inspector's 'pickColorFromPage' method can be called (from
the inspector toolbar or from the color-picker in the ruleview).
Before this change, it was possible to show several eyedropper because
these 2 codepaths didn't know about each other.
Now, when executing the gcli command, the inspector's
'cancelPickColorFromPage' method is called to hide it first.
And, when the 'pickColorFromPage' method is called, the 'eyedropper --hide'
gcli command is called too.
This way, there's only one eyedropper shown.
There was also a problem where the gcli command would create a new
eyedropper everytime it was called. This was fixed too, by maintaining a
WeakMap of all eyedroppers opened so far.
MozReview-Commit-ID: F6fBP5R7ZTJ
--HG--
extra : rebase_source : f04bbf224ced7b93b4e5b0c42662731ecc58cb58
Patrick Brosset
Sebastian Hengst
Paolo Amadini
Luca Greco
J. Ryan Stinnett
Alisha
Boris Zbarsky
Alexandre Poirot
Michelangelo De Simone
Wes Kocher
Tim Nguyen
Florian Quèze
gtatum@mozilla.com
JerryShih
Julian Descottes
Gabriel Luong
Phil Ringnalda
Tom Tromey
Daisuke Akatsuka
Greg Tatum
Eddy Bruel