This cleans up a bit and allows us to be smarter about which cursors
should we allow from content or what not, which will help with bug 1445844 and
co.
Differential Revision: https://phabricator.services.mozilla.com/D16711
They were incorrectly pointed at the non-partner configs in 2e27f3f1ebc6f38d98ddd42b6955083f637e2b1b.
Differential Revision: https://phabricator.services.mozilla.com/D17716
--HG--
extra : moz-landing-system : lando
DisplaySystemMenu() does not handle nsSizeMode_Invalid that causes warning of
clang. This patch makes it treat nsSizeMode_Invalid. When it receives the
value, it will call NS_ASSERTION() to be detectable on debug builds during
automated tests.
Additionally, this adds default case into the switch statement with
MOZ_ASSERT_UNREACHABLE(). Then, when somebody adds new nsSizeMode, they
can detect it with crash in debug build if they forget to change this method.
Differential Revision: https://phabricator.services.mozilla.com/D17217
--HG--
extra : moz-landing-system : lando
The method was added by bug 506926, but not sure when this becomes an orphan.
Differential Revision: https://phabricator.services.mozilla.com/D17215
--HG--
extra : moz-landing-system : lando
We can always pull this back from history should we need it, but given
how broken the texture caching of pictures was (see the recent text shadow
story) I suspect we won't.
Differential Revision: https://phabricator.services.mozilla.com/D17524
Added "space-in-parens": ["error"] to eslint for passwordmgr, and fixed the 5 errors found.
Differential Revision: https://phabricator.services.mozilla.com/D17697
--HG--
extra : moz-landing-system : lando
I haven't managed to find a way stuff should unexpectedly die around these
functions, so add a few diagnostics to catch this hopefully, before papering
over the bug / backing out / adding a kungfudeathgrip.
Differential Revision: https://phabricator.services.mozilla.com/D17514
--HG--
extra : moz-landing-system : lando
This also moves the label from ScriptLoader::ProcessScriptElement to
ScriptLoader::EvaluateScript so that it also kicks in for scripts that are run
from NotifyOffThreadScriptLoadCompletedRunnable::Run.
Differential Revision: https://phabricator.services.mozilla.com/D14924
--HG--
extra : moz-landing-system : lando
Move prefs from pwmgr_common.js to mochitest.ini and remove redundant calls to set those same prefs.
Differential Revision: https://phabricator.services.mozilla.com/D17589
--HG--
extra : moz-landing-system : lando
NSS 3.42 added a new build flag, enable_sslkeylogfile, to toggle the
availability of the SSLKEYLOGFILE variable (see Bug 1515236 and Bug 1519209).
Differential Revision: https://phabricator.services.mozilla.com/D17588
--HG--
extra : moz-landing-system : lando
The changes were made in Github to have proper markup for the
SmartTrace component. In the console, we change how the "Copy Message"
and "Export visible messages" context menu actions work so they use
the Selection API instead of `element.textContent`.
The Selection API reflects what would happen if a user do a text
selection, so having our actions to do the same ensure that we keep
our markup suitable for the clipboard.
Differential Revision: https://phabricator.services.mozilla.com/D17378
--HG--
extra : moz-landing-system : lando
Having the element displayed as a block cause some new lines
to be added the clipboard when doing a selection and copying.
This would also break the changes we are doing in the "Copy message"
context menu entry.
Differential Revision: https://phabricator.services.mozilla.com/D17377
--HG--
extra : moz-landing-system : lando
The Frames component changed significantly on Github, which means
we need to do some adjustments in the SmartTrace component (pass
the `selectable` prop, change CSS rules, …).
For now, we also hide the Framework icons as we need to find a way
to properly share the underlying CSS from the debugger (See
https://github.com/devtools-html/debugger.html/issues/7782).
Differential Revision: https://phabricator.services.mozilla.com/D17376
--HG--
extra : moz-landing-system : lando
This is needed to test the test harness's handling of a negative leak
being reported by the XPCOM leak checker.
Depends on D17535
Differential Revision: https://phabricator.services.mozilla.com/D17536
--HG--
extra : moz-landing-system : lando
In order to test the test harness's handling of a process failing to
produce a leak log, add a special function that disables the bloat log
output.
Differential Revision: https://phabricator.services.mozilla.com/D17534
--HG--
extra : moz-landing-system : lando
It fixes the regression from the transition to Serde (bug 1396821),
which accidentally denied unknown fields.
Differential Revision: https://phabricator.services.mozilla.com/D17634
--HG--
extra : moz-landing-system : lando
This patch applies the following changes:
- Reduce the chances of retrieving the initial popup panel size while it is resizing, by comparing the
content dimensions retrieved before and after the delay (which is already set to a value comparable
to the time used by the resize debouncing timer), and wait until both the dimensions collected are the same
- split browser_ext_browserAction_popup_resize.js into two test files (as it seems, based on the investigations
I did by reproducing this intermittent locally, that the part that can still fail intermittently from time
to time with the change describe above is related to the testBrowserActionMenuResizeBottomArrow test case)
- move the test helpers shared between the two test files into a new head_browserAction.js support file
- re-enabled browser_ext_browserAction_popup_resize.js
- mark the new browser_ext_browserAction_popup_resize_bottom.js as disabled on debug build,
because it is consistently triggering a "shutdown leak" failure when running locally
Differential Revision: https://phabricator.services.mozilla.com/D17267
--HG--
rename : browser/components/extensions/test/browser/browser_ext_browserAction_popup_resize.js => browser/components/extensions/test/browser/browser_ext_browserAction_popup_resize_bottom.js
rename : browser/components/extensions/test/browser/browser_ext_browserAction_popup_resize.js => browser/components/extensions/test/browser/head_browserAction.js
extra : moz-landing-system : lando
Add a scalar 'autoplay_default_blocked' which records a boolean value which indicates whether user is blocking autoplay by default.
Differential Revision: https://phabricator.services.mozilla.com/D17298
--HG--
extra : moz-landing-system : lando
