The only user is nsFileControlFrame, which can just use the attribute change
callback instead to sync the disabled attribute value with the button.
Syncing tabindex in that attribute callback was wrong since bug 505355.
Differential Revision: https://phabricator.services.mozilla.com/D68740
--HG--
extra : moz-landing-system : lando
This copies assertions from existing actor/front tests in order to be able to later
drop startListeners and getCachedMessages on the console actor.
Differential Revision: https://phabricator.services.mozilla.com/D67531
--HG--
extra : moz-landing-system : lando
This demonstrates using the Resources API for the console messages,
using the existing actor methods. It helps proving that this will work against old runtimes.
But the plan is to followup in bug 1620243 so that we implement this code on the server side.
This will help getting rid of this LegacyImplementation code and have a simplier code on the server.
Differential Revision: https://phabricator.services.mozilla.com/D65526
--HG--
extra : moz-landing-system : lando
This focus on implementing a client side version of the Resources API.
This helps demonstrate that this API can works against existing and old Firefox runtimes, using existing actor APIs.
A following changeset (bug 1620243) will introduce a server-side implementation, which will help listening to resources early.
And will help getting rid of the LegacyListeners object which is introduced by the next changeset (bug 1620234).
Differential Revision: https://phabricator.services.mozilla.com/D65527
--HG--
extra : moz-landing-system : lando
The lazy service function has tons of unused parameters that we might as well
clean up, and the require getter can easily used more shared code for its
implementation.
Differential Revision: https://phabricator.services.mozilla.com/D67982
--HG--
extra : moz-landing-system : lando
These all look like they were changed to be lazy to allow for features of
WebReplay to swap out the implementations, but now that Replay has been
removed from the codebase, these can be treated the same way other globals are.
Differential Revision: https://phabricator.services.mozilla.com/D67981
--HG--
extra : moz-landing-system : lando
Since base-loader's job is to handle this kind of thing, and it already
requires a special case to populate the descriptor anyway, so it seems a lot
easier to provide this as builtin optional feature of base-loader.
Differential Revision: https://phabricator.services.mozilla.com/D67979
--HG--
extra : moz-landing-system : lando
I can't see any reason why these need to be scoped into the per-file target
environment, and they both feel like strange special cases, so might
as well remove them now.
Differential Revision: https://phabricator.services.mozilla.com/D67978
--HG--
extra : moz-landing-system : lando
This is never used so it seems like there isn't much reason to keep it around.
Differential Revision: https://phabricator.services.mozilla.com/D67977
--HG--
extra : moz-landing-system : lando
This module doesn't appear to ever be used, and we already provide setTimeout
and such as globals so presumable we're using those in the places where we
need functional timers.
Differential Revision: https://phabricator.services.mozilla.com/D67976
--HG--
extra : moz-landing-system : lando
These functions don't appear to ever be used by devtools since we instead
use the `loader.lazyRequireGetter` utility.
Differential Revision: https://phabricator.services.mozilla.com/D67975
--HG--
extra : moz-landing-system : lando
Correcting linter errors
Added new logic for toggling control frames by adding a new control frame check variable and toggle function
Preserve controlFrames option when clearing frames. Changed Control Frames to Control in locale
Correct linter errors
Added a separator between received and control. Changed the dropdown title to reflect control frame state
Changed controlFramesEnabled to showControlFrames
Added a comment about showControlFrames and toggleControlFrames
Differential Revision: https://phabricator.services.mozilla.com/D67849
--HG--
extra : moz-landing-system : lando
This patch changes the Content Processes names from
'Content Process 1234' to 'Content Process (pid 1234)',
which is less confusing for the user.
Differential Revision: https://phabricator.services.mozilla.com/D68328
--HG--
extra : moz-landing-system : lando
`inputmode` is lower case except to `mozAwesomebar`. So it is unnecessary to
use `equalsIgnoreCase`.
Also, `mozAwesomebar` is for `inputmode`, not `type`. So this changeset has
this fix.
Differential Revision: https://phabricator.services.mozilla.com/D68332
--HG--
extra : moz-landing-system : lando
`inputmode=none` has to close software keyboard. `inputmode` value is lower
case except to `mozAwesomebar` by bug 1618763, so we don't have to use
`equalsIgnoreCase` for `inputmode`.
Differential Revision: https://phabricator.services.mozilla.com/D67459
--HG--
extra : moz-landing-system : lando
Make the JSON tree view more accessible.
1. Automatically set focus to the first node on initial focus. Previously, the only way to interact with the tree view through the keyboard was to click on a node so that subsequent key presses would register.
2. Fix inaccurate aria-level and aria-expanded attributes causing confusing announcements for screen reader users.
3. Previously, pressing left arrow the first time on a leaf child node would not move focus to its parent, but subsequent tries would work. This has been fixed.
4. Implement first-letter navigation for quick movement via keyboard.
Differential Revision: https://phabricator.services.mozilla.com/D28274
--HG--
extra : moz-landing-system : lando
