WebAnimations API is not enabled by default in all release channels yet.
It is behing the pref dom.animations-api.core.enabled.
Turn the preference on before any test of the animationinspector, and
clear it after the test.
MozReview-Commit-ID: K8UXEthLhnH
--HG--
extra : rebase_source : c20aad209c3bd47b4e76ba05f3ca675fc86ed92a
extra : histedit_source : b09656b90a57beb684d84e7571f16cd36d6d0f7b
When receiving a console clear message, the webconsole should clear
the UI: remove all messages until the clear() message and close
the variables view sidebar if opened.
Add one integration tests to test console.clear calls from the content page.
MozReview-Commit-ID: GnBCBSmN1rk
--HG--
extra : rebase_source : 3bb9f99fa4ac8ed6772e325dba978ce3e6a0f202
extra : source : 671011b82100a598dd8368205bd625227bfdc060
There was an error thrown in the stylesheet.js `dirname` function because of
`this.safeURL` being like "blob:XXX", and thus not being valid for `Services.io.newURI`.
Removing the "blob:" part of the safeUrl before calling the `dirname` function
resolves the bug.
MozReview-Commit-ID: 9uth6vyAR2u
--HG--
extra : transplant_source : %82%09%7D%9F%0E%8F%B4%BA%A6%22%E3%B1%98%ADN%22%5B%00q%B2
When receiving a console clear message, the webconsole should clear
the UI: remove all messages until the clear() message and close
the variables view sidebar if opened.
Add one integration tests to test console.clear calls from the content page.
MozReview-Commit-ID: GnBCBSmN1rk
--HG--
extra : rebase_source : b26481845b5deb4213c6d25581d37e8eda3e17a7
This test wasn't using refreshState, instead it used getCurrentState.
What refreshState does on top of getCurrentState is it stores the new state
locally.
getCurrentState isn't meant to be called externally, it is only meant to be
an actor method interceptor that reconstructs the missing state.
So the test should have used refreshState from the start.
Turns out it worked in most cases because the animation did have a startTime
when the test retrieved it, so it had a previousStartTime.
But, if for some reason, the animation has a startTime=null when the test
starts, then the value never gets to the front, and bad things happen.
MozReview-Commit-ID: 2nEIKHMHsCS
--HG--
extra : rebase_source : 14d896fe895876346f1d52c3e8f72880d5bdfec6
js::Class op are often all null. And when they're not all null, they're often
duplicated among classes. By pulling them out into their own struct, and using a
(possibly null) pointer in js::Class, we can save 114 KiB per process on
64-bit, and half that on 32-bit.
* * *
imported patch separate-ClassOps-2
--HG--
extra : rebase_source : bd751bf247e9491c1966a123dbeffa573657dfb1
This adds the INDIVIDUALS view state to the memory panel, renames "dominator
tree display" to "label display", and adds a view for listing the individual
nodes in a census group and inspecting each nodes' retaining paths.
--HG--
rename : devtools/client/memory/actions/dominator-tree-display.js => devtools/client/memory/actions/label-display.js
rename : devtools/client/memory/reducers/dominator-tree-display.js => devtools/client/memory/reducers/label-display.js
There was an error thrown in the stylesheet.js `dirname` function because of
`this.safeURL` being like "blob:XXX", and thus not being valid for `Services.io.newURI`.
Removing the "blob:" part of the safeUrl before calling the `dirname` function
resolves the bug.
MozReview-Commit-ID: 9uth6vyAR2u
--HG--
extra : transplant_source : %1F%14%BA%13%8A%FC9%22%E5%F4%F8%B7%E93%DF%24%88G7R
Jarda Snajdr
Kumar McMillan
Julian Descottes
Carsten "Tomcat" Book
Wes Kocher
Patrick Brosset
Yura Zenevich
Tom Schuster
Eddy Bruel
Brian Grinstead
Greg Tatum
Alexandre Poirot
Nicolas Chevobbe
Chris Peterson
Nicholas Nethercote
Kartikaya Gupta
Phil
Nick Fitzgerald
Andrew Swan
Jason Laster
Ryan VanderMeulen