Make toolkit/components/passwordmgr/test/test_xml_load.html work with e10s
Differential Revision: https://phabricator.services.mozilla.com/D17715
--HG--
rename : toolkit/components/passwordmgr/test/test_xml_load.html => toolkit/components/passwordmgr/test/mochitest/test_xml_load.html
extra : moz-landing-system : lando
* Added browser_private_window.js - which is a port of chrome/privbrowsing_perwindowpb.html
* Moved onload/form submit from the form documents to the test via ContentTask.spawn
* The test which verifies autofill doesnt work in private windows, but autocomplete does - is disabled for now and bug 1523777 filed to re-enable it.
Differential Revision: https://phabricator.services.mozilla.com/D17676
--HG--
extra : moz-landing-system : lando
Fixes leak where the return value of GetManifestContents in updater.cpp is not freed
Fixes leak where the return value of get_quoted_path in updater.cpp is not freed
Fixes leak in nsUpdateDriver.cpp ApplyUpdate
With these leaks fixed the UI tests that stage updates can run on Linux asan
Differential Revision: https://phabricator.services.mozilla.com/D17910
--HG--
extra : moz-landing-system : lando
Bug 730495 broke them by moving the code to another directory without
moving the corresponding #define, but it also fixed why this was
disabled in some configurations so we can now just enable when
MOZ_MEMORY is defined (jemalloc used).
Differential Revision: https://phabricator.services.mozilla.com/D18049
--HG--
extra : moz-landing-system : lando
The addition of the Carbon.h include to CreateAppData.cpp is to ensure that
The OSX API headers are used before conflicting symbols are declared in the
mozilla namespace.
Differential Revision: https://phabricator.services.mozilla.com/D16718
--HG--
rename : toolkit/xre/nsCommandLineServiceMac.cpp => toolkit/xre/nsCommandLineServiceMac.mm
extra : moz-landing-system : lando
Make toolkit/components/passwordmgr/test/test_xml_load.html work with e10s
Differential Revision: https://phabricator.services.mozilla.com/D17715
--HG--
rename : toolkit/components/passwordmgr/test/test_xml_load.html => toolkit/components/passwordmgr/test/mochitest/test_xml_load.html
extra : moz-landing-system : lando
Limit the number of commands shown per extension in the shortcuts UI. A show
more button is included to show all of the commands for a given extension if
there are more than the limit.
Differential Revision: https://phabricator.services.mozilla.com/D17878
--HG--
extra : moz-landing-system : lando
Commands that have a shortcut will be listed first in the extension shortcut UI.
Differential Revision: https://phabricator.services.mozilla.com/D17877
--HG--
extra : moz-landing-system : lando
Prevent adding commands to private windows when extensions do not have permission.
Differential Revision: https://phabricator.services.mozilla.com/D17414
--HG--
extra : moz-landing-system : lando
Based on what I've been able to reproduce locally using --verify, there is a chance that
the notifications created by the test case named `test_notifications_populated_getAll`
may have been removed before the `browser.notifications.getAll` is going to retrieve them,
and when this happens the test gets stuck because `browser.test.notifyPass("getAll populated");`
is never reached, and the test timeouts.
This patch includes the following changes to prevent the intermittent failure described above:
- add a new head_notifications.js support file and create a new MockAlertsService test helper that
loads a chrome script which replace the alerts service with a mock service (based on a
similar mock defined in dom/notification/test/mochitest/MockServices.js), the mocked alert
service doesn't close the notification until the test case itself has called
`MockAlertsService.clearNotifications` (so that the test shouldn't fail intermittently as
described above).
- applies the changes needed on test_ext_notifications.html to make use of the MockAlertsService
Differential Revision: https://phabricator.services.mozilla.com/D17863
--HG--
rename : dom/notification/test/mochitest/MockServices.js => toolkit/components/extensions/test/mochitest/head_notifications.js
extra : moz-landing-system : lando
This patch should fix the test_ext_sendmessage_reply2.html intermittency which, based on the
timeout failure that I've been able to intermittently reproduce when running this test
locally using --verify, seems to be likely due to the following race:
the tabs.create API (used to create the extension tabs used as part of the tests) was called
right before subscribing the extension message listeners, and so from time to time the
extension tabs were not able to successfully send their messages to the background page listeners
(because the background page didn't subscribe the listeners yet) and as a result the test was getting
stuck waiting for extension messages that were never going to be received.
Differential Revision: https://phabricator.services.mozilla.com/D17849
--HG--
extra : moz-landing-system : lando
We reenable the corresponding tests unconditionally because we don't run
tests on the msvc builds anyways (and they're going to be retired soon).
Differential Revision: https://phabricator.services.mozilla.com/D18028
--HG--
extra : moz-landing-system : lando
This patch includes the following changes:
- added a new "num_strings" extra key to the "addonsManager install" and "addonsManager manage"
telemetry events, where "num_strings" represents the "number of permissions actually visible
in the extension permission doorhanger"
- do not record a telemetry event for the "permission_prompt" (or "sideload_prompt") if the
permissions_prompt is not going to be shown
- add num_strings and removed "num_perms" and "num_origins" extras from the test assertions in the existing tests
- added some additional assertions to test in automation that we don't record the telemetry
event for "permission_prompt" when no permission prompt is being shown for an
extension update (as part of the browser_extension_update_background_noprompt.js test)
Differential Revision: https://phabricator.services.mozilla.com/D16992
--HG--
extra : moz-landing-system : lando
