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
ESLint 2 now flags anonymous generator functions according to
generator-star-spacing. Most of the changes here are correcting that.
MozReview-Commit-ID: 9xg2Gmlaz94
--HG--
extra : rebase_source : e6db0fd0ef477cd4fd2196b1036783f0974c586b
extra : histedit_source : 03eea033884969cc2a340316377318b0487ebdf2
The collapsible sidebar has min-height:35vh and max-height:75vh
when viewport-width < 700px (ie vertical layout).
These bounds should not apply when the panel is collapsed. The
collapsing relies on negative margins to hide the panel, which
can only work if the computed height remains constant once the
panel has been collapsed.
Added a new mochitest checking that the height and margin-bottom
are constant through a layout switch.
MozReview-Commit-ID: K6EGiBtJ11S
--HG--
extra : rebase_source : 5141f4610b586c32158d0b3ee2f50fda230f3c05