I think we have a special edge case here, where we do have a navigation,
but no new top level target is notified.
In regular devtools/webpages, we should have a new top level target notified to the debugger.
Differential Revision: https://phabricator.services.mozilla.com/D156467
Now that the script is run on automation, there's no need to have
a (different) version in tree.
The documentation is also updated to explain the current setup.
Differential Revision: https://phabricator.services.mozilla.com/D156930
This will help transition to ES Modules as this symbol is exposed to them.
$ sed -ie "/require(.ChromeUtils.)/d" $(git grep -l 'require("ChromeUtils")' devtools/)
$ sed -ie "/loader.lazyRequireGetter(this, .ChromeUtils./d" $(git grep -l 'loader.lazyRequireGetter(this, "ChromeUtils"' devtools/)
+ the edition of builtin-modules.js + eslintrc.js + manual eslint fixes
Differential Revision: https://phabricator.services.mozilla.com/D156402
This will help transition to ES Modules as this symbol is exposed to them.
$ sed -ie "/require(.Services.)/d" $(git grep -l 'require("Services")' devtools/)
$ sed -ie "/loader.lazyRequireGetter(this, .Services./d" $(git grep -l 'loader.lazyRequireGetter(this, "Services"' devtools/)
+ the edition of builtin-modules.js + eslintrc.js
+ manual eslint fixes
+ removal of devtools-services in the debugger, except for jest tests
Differential Revision: https://phabricator.services.mozilla.com/D156401
It's always true, so remove it.
Add another pref to allow -webkit-line-clamp to work on all blocks
rather than just legacy -webkit-boxes, which seems something we should
try to look into, eventually.
Depends on D155181
Differential Revision: https://phabricator.services.mozilla.com/D155182
This allows to keep the DevTools visible while interacting with the Firefox
window where the extension is running.
This behavior is enabled by default, but can be disable on-demand via a button
in the top toolbar.
Note that it requires to close and reopen the window/toolbox as platform APIs
disallow changing this behavior "live" on a given window.
Differential Revision: https://phabricator.services.mozilla.com/D155843
Depends on D156655
system stylesheets cannot be disabled, apply a dedicated classname on the summary and disable the visibility toggle
Differential Revision: https://phabricator.services.mozilla.com/D156082
Right now, the vertical position of the status panel is the "auto"
position, which ends up working out, but mostly by chance, and relies on
behavior that's different from the standard flexbox, see bug 1789165.
Instead of using `position: fixed` and relying on not having any
sidebars or other content to the inline-end (otherwise the [mirror] rule
would be incorrect), explicitly position it against the
.browserContainer.
Differential Revision: https://phabricator.services.mozilla.com/D156384
In StyleSheetsManager _getMediaRules, we were only looping
over document.cssRules, and as a result were missing potential
nested media queries.
For each rule, we now go other its potential cssRules, recursively,
to gather all media query rules.
Test cases are added for the client to make sure that those nested
rules do show up in the StyleEditor media queries sidebar.
Differential Revision: https://phabricator.services.mozilla.com/D156277
Two issues fixed:
- when sorting on one column, other column content should be re-arranged
- natural order sort was not symmetrical for dates and led to inconsistent sorting
Differential Revision: https://phabricator.services.mozilla.com/D156420
In md files and code comments and mostly from common js files.
I'm moving away from require to load sys.mjs files so that we are closer
to what we do in mozilla-central.
Differential Revision: https://phabricator.services.mozilla.com/D154073
This patch adds reverts back to having distint context menu items for 'Resend' and 'Edit and Resend'
but this is using the new http custom request functionality.
Differential Revision: https://phabricator.services.mozilla.com/D155159
Since we already had a test case for nested at-rules in
browser_rules_container-queries.js, I'm moving it to a
new test where we can test all the different at-rules that
can be nested (including `@supports`).
Differential Revision: https://phabricator.services.mozilla.com/D156313
`ChromeUtils.dateNow()` has a higher precision than `Date.now()`, which is useful for ordering
of messages in the console output.
Differential Revision: https://phabricator.services.mozilla.com/D155548
We can get a higher precision timestamp from microSecondTimeStamp, which will be consumed
in the console client to re-order messages.
This fixes an issue where different type of resources (console-messages and error-messages)
emitted during the same timestamp would not appear in the order they should be in.
A test is added to make sure the fix is effective.
Differential Revision: https://phabricator.services.mozilla.com/D155546
Note that it will also stop showing locale and popup settings for remote browser toolboxes.
Toolbox.isBrowserToolbox being false for this usecase.
Differential Revision: https://phabricator.services.mozilla.com/D155956
_buildTabs/_setInitialMeatballState wasn't awaited for.
So that preference front request might be pending when closing the toolbox too quickly in tests.
We should wait for all RDP requests to be completed before resolving Toolbox.open.
Differential Revision: https://phabricator.services.mozilla.com/D155872
It looks like there was some (hardware?) changes on TRY
which caused the test to run in Coordinated Universal Time
timezone, when one test expect it to be CEST.
We force the timezone in the test command so it will
always be CEST.
Differential Revision: https://phabricator.services.mozilla.com/D155818
Henrik Skupin
Emilio Cobos Álvarez
Nicolas Chevobbe
Mark Banner
Alexandre Poirot
Hubert Boma Manilla
Mariana Picolo
justchen1369
Noemi Erli
Julian Descottes
Olli Pettay
lyavor
Rob Wu
Sylvestre Ledru