This adds support for container tabs / contextual identity in Responsive Design
Mode. Tabs in non-default contexts can now be opened in RDM just like regular
tabs.
MozReview-Commit-ID: BofTgrowjGV
--HG--
extra : rebase_source : 171f6d0579ef3528160729b964d1cc71e1d74386
Some of the RDM toolbar icons relied on `background-size: cover` from the
overall DevTools button styles, which was removed recently in bug 1442531. We
restore RDM's appearance by copying this style into RDM styles.
MozReview-Commit-ID: KcZwaRgZUsh
--HG--
extra : rebase_source : 4a2f548f6f073870ad06183a33bdaabc2bff6d92
The methods have been improved and now live in telemetry.js again.
We use these methods for tools that at least require timing.
MozReview-Commit-ID: 2CqBCA9j3XU
--HG--
extra : rebase_source : faa489ea4790db55648301be842f55cea308ce29
Also fixes existing code which fails the rule.
MozReview-Commit-ID: CkLFgsspGMU
--HG--
extra : rebase_source : 86a43837659aa2ad83a87eab53b7aa8d39ccf55b
Use `E10SUtils` to check for cases where browser code would try to force a
browser to reselect a new process (such as when it is a preloaded browser) so
that we can avoid any process changes once RDM is open.
If such a case applies, navigate to about:blank first to trigger the process
change before starting RDM.
MozReview-Commit-ID: CxspLFXXotF
--HG--
extra : rebase_source : cb94789344f17c0b51ff4afbb54921218a2dd1b5
Changes and notes:
- Created `devtools/client/shared/test/telemetry-test-helpers.js`, which
contains test helpers to aid in creating and running telemetry tests.
- Removed any telemetry monkeypatching as it is not dependable and no longer
needed (there is some left in GCLI but the test is now disabled because
we are removing GCLI soon anyhow).
- Because `telemetry-test-helpers.js` is imported by `shared-head.js` I
have had to make it available everywhere that shared-head.js is used.
- All telemetry tests have been rewritten to use the new helper.
- shared-head.js cannot be imported by tests inside
`devtools/client/performance/test/` because perf have custom `once` and
`waitFor` implementations that act differently from the ones inside
`shared-head.js`. This means I had to import the telemetry helpers into
`devtools/client/performance/test/head.js`
- Created `devtools/client/shared/test/browser_telemetry_misc.js` to be sure
to catch `DEVTOOLS_SCREEN_RESOLUTION_ENUMERATED_PER_USER` (we catch a few
others to be thorough).
- Disabled `browser_inspector_menu-02-copy-items.js`, which was failing to
test some expired scalars. I also corrected the way the scalars are logged
because it was completely wrong.
MozReview-Commit-ID: JjQEGM6hT61
--HG--
extra : rebase_source : cd1214d01bd11908f69167839975cd93ecb83421
Manually-implemented QueryInterface functions don't benefit from the
MozQueryInterface optimizaions, and a lot of them are in hot code, and
implement a large number of interfaces.
MozReview-Commit-ID: 8OzglraowZt
--HG--
extra : rebase_source : 5fff3d9973a0ea976096339a63ce9ff628b68441
This also removes any redundant Ci.nsISupports elements in the interface
lists.
This was done using the following script:
acecb401b7/processors/chromeutils-generateQI.jsm
MozReview-Commit-ID: AIx10P8GpZY
--HG--
extra : rebase_source : a29c07530586dc18ba040f19215475ac20fcfb3b
This bounced because I was trying to access the toolbox after the ui was destroyed, which fails in tests. I will do a try run this time to make sure there are no issues.
MozReview-Commit-ID: 2iHpPLmm9lY
--HG--
extra : rebase_source : 42b0fbbfc26d43c49b699ef447c7650c94bd81ca
Another simple one... tests will be in bug 1456103.
MozReview-Commit-ID: 2iHpPLmm9lY
--HG--
extra : rebase_source : 7ca5153ae0e4137fe4f6da62cde52deb4f40579e
Another simple one... tests will be in bug 1456098.
MozReview-Commit-ID: LFgxlceCakC
--HG--
extra : rebase_source : b0b901b3b225277ce20aab9154c52896d14199fa
RDM frames with their custom message manager hadn't exposed a value for
`processMessageManager`. This was just a oversight.
By adding this value, we get a working Browser Content Toolbox for RDM tabs.
MozReview-Commit-ID: 95QskEMKgZK
--HG--
extra : rebase_source : 5259800f64afe55ee5bca29492f6f33efcfd458c
Move and rename the server's frame script that starts DevTools in remote frames
from `child.js` to `startup/frame.js`. `connectToChild` also becomes the more
generic `connectToFrame`. A few b2g-isms like "app" are also removed.
These code paths will likely change more as Site Isolation work continues, but
for now, we have this light cleanup to gather startup-related paths together.
MozReview-Commit-ID: El8a0OE99gZ
--HG--
rename : devtools/server/child.js => devtools/server/startup/frame.js
rename : devtools/server/tests/mochitest/test_connectToChild.html => devtools/server/tests/mochitest/test_connectToFrame.html
extra : rebase_source : 2735c53587257b215d720204cf7c4581088eba42
The shims that this rule tests for no longer exist.
MozReview-Commit-ID: DMgP7Hczavc
--HG--
extra : rebase_source : 765ddd5c62c9449c07ed050e44d86a3bd5c0ae64
extra : amend_source : 627a7694ac07182200f876901ded7a34721cd228
This removes the sync reflow from almost all cases. The only case where we keep it is when a keypress
caught in content triggers a sync message to the parent process. We should clean this up in bug 1371523.
I've tried to fix the tests, but a lot of them seem to be disabled anyway...
MozReview-Commit-ID: 9k36p7q8MKy
--HG--
extra : rebase_source : 311ee41ba9456a5c5d58b81a0cfa999bcef0027e
This removes the sync reflow from almost all cases. The only case where we keep it is when a keypress
caught in content triggers a sync message to the parent process. We should clean this up in bug 1371523.
I've tried to fix the tests, but a lot of them seem to be disabled anyway...
MozReview-Commit-ID: 9k36p7q8MKy
--HG--
extra : rebase_source : 311ee41ba9456a5c5d58b81a0cfa999bcef0027e
Ensure remoteWebProgress is initialized for remote browsers. Includes devtools fix from jryans.
MozReview-Commit-ID: Ce3TzwkNnyi
--HG--
extra : rebase_source : 0f2bcb96ef04f4eaee447180dc21400dca3bf410
By moving only the rejections that actually still apply into each test and out
of the shared head file, we are much more likely to notice new instances and
catch them when writing and editing tests in the future.
Bug 1018184 can be used to actually resolve these issues.
MozReview-Commit-ID: Qb71PsuutB
--HG--
extra : rebase_source : 7056bbf9fcd76ffe00015119d811db0bd788aa59
RDM was explicitly forcing the remote browser XBL binding via inline style, but
that's actually redunant with what you'd get via CSS. (I am unsure if that's
always been true...)
It appears we can safely remove this to reduce some complexity here.
MozReview-Commit-ID: 2xlS6Dd2VYj
--HG--
extra : rebase_source : 2f9eb8789650e96cf82be60e7fe07d2bb3159a91
The first time RDM is opened after this, show a notification explaining that a
reload is needed to apply certain emulation features.
MozReview-Commit-ID: 26GMbhT5MUo
--HG--
extra : rebase_source : 6b043a6465687ccae23eb2cf0619b3e82ca62c5f
This adds a menu to the RDM global toolbar to allow the user to control whether
the page reloads in response to various state changes.
This also changes the default behavior to _not_ reload, so that we avoid losing
changes that might have been made in DevTools.
MozReview-Commit-ID: 86h5cB5dify
--HG--
extra : rebase_source : 0d1598bd0ad066eaffdc23d4c970c64f368afa04
The first time RDM is opened after this, show a notification explaining that a
reload is needed to apply certain emulation features.
MozReview-Commit-ID: 26GMbhT5MUo
--HG--
extra : rebase_source : 069ab687830faf29e5fe37b408628c0cd85e1464
J. Ryan Stinnett
Julian Descottes
Michael Ratcliffe
Alexandre Poirot
Kris Maglione
Jan Odvarko
Ciure Andrei
shindli
Dão Gottwald
Nicolas Chevobbe
Tim Nguyen
Margareta Eliza Balazs
Gijs Kruitbosch
Brindusan Cristian
Shane Caraveo
Cosmin Sabou
Florian Quèze
arthur.iakab