The FrameLoaderOwner interface has been implemented in WebIDL for several
years now, so these QIs are simply unnecessary overhead.
MozReview-Commit-ID: LAzvfm5Qhy0
--HG--
extra : rebase_source : 2495c07df21c474f5fabc257ff4db43b0d8047e4
Expose an API to retrieve devtools' WebExtensionInspectedWindowFront which is needed
for webextensions. Exposed a new API on devtools/DevToolsShim
MozReview-Commit-ID: Dyc2UUJGsrs
--HG--
extra : source : b7435cd66ce3299d23f71a9bf855edbcb1ccacf2
Removing dependencies from mozilla-central to devtools. Use DevTools shim instead
of directly depending on devtools code here.
MozReview-Commit-ID: CeV5tfw1Vnz
--HG--
extra : source : 22baf4e67730ce89d5342cb0dd5c1e2e5944b4a1
Expose an API to retrieve devtools' WebExtensionInspectedWindowFront which is needed
for webextensions. Exposed a new API on devtools/DevToolsShim
MozReview-Commit-ID: Dyc2UUJGsrs
--HG--
extra : rebase_source : 018660cc54bf2454c1f810ded639fd647ba79da3
Removing dependencies from mozilla-central to devtools. Use DevTools shim instead
of directly depending on devtools code here.
MozReview-Commit-ID: CeV5tfw1Vnz
--HG--
extra : rebase_source : 515278b93ad9840f6af89fb13cc62bb819a65253
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
--HG--
extra : rebase_source : 33f1a2183ee717c79f360a7dda688832a5c33566
After Bug 1359855, the developer toggle is added to CustomizableUI via devtools-startup.
It is added after browser-delayed-startup-finished is received. However when starting
devtools with --jsconsole, devtools will be initialized before we receive the event and
the toggle will never be added to the UI.
Introducing a new flag here dedicated to the developer toggle and adding a few comments
to the devtools-startup:hookWindow() method which becomes a bit complex now.
MozReview-Commit-ID: IhPFznt0O83
--HG--
extra : rebase_source : d282e39c0588fca29813305292e53e71f93814bd
DevTools preferences are loaded dynamically by calling DevtoolsPreferences.loadPrefs().
We can not preload them when the addon starts, otherwise this will slow down the startup
of Firefox.
But jsonview's converter-observer needs to check preferences to check if jsonview is
enabled very early. Moving devtools.jsonview.enabled to a separate preferences file
that is still processed by firefox fixes the issue.
The downside is that this pref will keep following m-c's release cycle and not the addon's.
But it is so generic it should not be a big issue.
MozReview-Commit-ID: HrD5IVe54Ks
--HG--
extra : rebase_source : bb85aa12ec92db7d11abdb002f0429123b173afd
extra : source : 9622410d90ad264933ee7d1147ed655615ac4a19
DevTools preferences are loaded dynamically by calling DevtoolsPreferences.loadPrefs().
We can not preload them when the addon starts, otherwise this will slow down the startup
of Firefox.
But jsonview's converter-observer needs to check preferences to check if jsonview is
enabled very early. Moving devtools.jsonview.enabled to a separate preferences file
that is still processed by firefox fixes the issue.
The downside is that this pref will keep following m-c's release cycle and not the addon's.
But it is so generic it should not be a big issue.
MozReview-Commit-ID: HrD5IVe54Ks
--HG--
extra : rebase_source : 7feb021770c827996e276b60169b08093ecc1ff0
WebExtension tests expect DevTools to be automatically initialized,
they access DevToolsShim.gDevTools.getTargetForTab in order to open DevTools.
MozReview-Commit-ID: 3VQRlxgBkI0
--HG--
extra : rebase_source : 66fe8aeef5314fe06ac59ae025b1321fcc1195fc
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
--HG--
extra : rebase_source : 1781edcf11316eab7e95cbab834d1bc3230c44d7
Use DevToolsShim to access devtools APIs from webextensions code.
For webextensions tests using DevTools, tests are accessing DevToolsShim.gDevTools
which is fine for test purposes.
MozReview-Commit-ID: 66gFV98xvpf
--HG--
extra : rebase_source : 05734afae4368c5d7e4682b5fae1b8f3e4417220
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
--HG--
extra : rebase_source : 3e4832bcaffa92d64e9d2490bcc0250bc05573c1
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
--HG--
extra : rebase_source : 17685611ae0270afd6b819043b56cda94511a723
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
--HG--
extra : rebase_source : 357b503532fed7933a6690418b846c70350c59b9
