This is pretty simple... finding the best locations for the probes was the
struggle here.
In order to land these probes before the freeze the test for these events will
be created as part of bug 1456073.
MozReview-Commit-ID: 7hIfbD3wQ1I
Both reason and isSlotted arguments of setNodeFront are optional, switching to an
object argument avoids weird calls such as setNodeFront(front, null, true) in favor
of a more explicit setNodeFront(front, { isSlotted: true });
MozReview-Commit-ID: A6nziH3QQYe
When inspecting a node with the toolbox focused on an inner frame, we need to
adjust the selectors used to remove hidden parent frames.
MozReview-Commit-ID: CXwb3FmnJFO
Reverse the array of node inspection selectors, so that are a bit more naturally
human-readable by starting from the root document and moving inwards.
MozReview-Commit-ID: BYXryJg7iR9
Using fill instead of filter we don't need to define each icon as
invertable or not. If the icon is a SVG and supports fill="context-fill"
then it will be inverted/highlighted etc... as expected.
If not then it won't be impacted by DevTools themes.
MozReview-Commit-ID: CLFprKMuCt9
Expose an API to retrieve devtools' WebExtensionInspectedWindowFront which is needed
for webextensions. Exposed a new API on devtools/DevToolsShim
MozReview-Commit-ID: Dyc2UUJGsrs
Expose an API to retrieve devtools' WebExtensionInspectedWindowFront which is needed
for webextensions. Exposed a new API on devtools/DevToolsShim
MozReview-Commit-ID: Dyc2UUJGsrs
This evolves restoreScratchpadSession into restoreDevToolsSession which can keep track
of more than just scratchpad windows. In this case we also restore the Browser Console.
MozReview-Commit-ID: D4vOGkpq8xH
As devtools become optional, nsContextMenu needs to check if devtools are installed before
displaying the devtools-related menu entries.
Rather than loading devtools classing and calling APIs, use APIs provided by the DevToolsShim,
that will stay in mozilla-central.
MozReview-Commit-ID: CxqabTjhckC
Some APIs and methods still used by the addon sdk are not worth exposing
or migrating to mozilla-central given that this is only intended for
release 56 (after that, legacy extensions will no longer be supported).
For those APIs, we create a simple wrapper in DevToolsShim and moved the
implementation to framework/devtools
MozReview-Commit-ID: 8LiiptqO0NI
Some APIs and methods still used by the addon sdk are not worth exposing
or migrating to mozilla-central given that this is only intended for
release 56 (after that, legacy extensions will no longer be supported).
For those APIs, we create a simple wrapper in DevToolsShim and moved the
implementation to framework/devtools
MozReview-Commit-ID: 8LiiptqO0NI
Some APIs and methods still used by the addon sdk are not worth exposing
or migrating to mozilla-central given that this is only intended for
release 56 (after that, legacy extensions will no longer be supported).
For those APIs, we create a simple wrapper in DevToolsShim and moved the
implementation to framework/devtools
MozReview-Commit-ID: 8LiiptqO0NI