This patch will do :
- replace the old pref with the new pref
The advantage of doing so :
- to ensure those tests can still use the correct blocking autoplay policy
Differential Revision: https://phabricator.services.mozilla.com/D73973
This patch will do :
- replace the old pref with the new pref
The advantage of doing so :
- to ensure those tests can still use the correct blocking autoplay policy
Differential Revision: https://phabricator.services.mozilla.com/D73973
`network.preload` is off by default and there for not representative of a user of Firefox. By removing that user preference we are more in line
Differential Revision: https://phabricator.services.mozilla.com/D71774
i.e. remove annotations that manually enable the property, and remove the
property_database.js check that tests for the property being enabled.
We've been shipping with the property enabled ever since Firefox 69, so we're
realistically not going to default-disable it at this point, which means these
annotations (and the property_database.js check) are just cruft.
Differential Revision: https://phabricator.services.mozilla.com/D69128
Use the PSL list to evaluate whether user typed strings in urlbar are valid URLs.
Cleanup the URIFixupInfo.fixupChangedProtocol property to be set appropriately.
Auto-correct the most common suffix typos for com, net, org.
Stop using URIFixup to trim urls when the urlbar value is set, instead always trim,
then untrim on focus if the trimmed string would cause, on navigation, a search
instead of a visit. This saves us from doing the URIfixup work on page load and
tab switch, running it only when strictly necessary.
Fix the "Did you mean to go to" prompt to show a protocol, avoiding the
confusing (but funny) "did you mean to go to 'space'" prompts.
Differential Revision: https://phabricator.services.mozilla.com/D68796
This patches fixes several problems found on Raptor and the condprof:
Raptor:
- Make sure the conditioned profile dir is removed after
it's been used, not before.
- Adds the --project option to raptor so we know if we're on try
autoland or mozilla-central.
- Both Fennec and Fenix are deactivated for now
- Use the allow-downgrade flag to be flexible on build ids (the next step will be bug 1628666)
Conditioned profiles, curation of the profile prefs:
- Fully deactivates Normandy during Raptor tests (app.normandy.enabled)
- Removes any GFX blacklisting (gfx.blacklist.*)
- Removes any marionette pref
- Enforce extensions sideloading (extensions.startupScanScopes)
Differential Revision: https://phabricator.services.mozilla.com/D70518
Deactivate tracing so we don't generate huge geckodriver logs
since BT transmits the profile through webdriver
Differential Revision: https://phabricator.services.mozilla.com/D70829
--HG--
extra : moz-landing-system : lando
This removes the obsolete backend. Notes on some of the less obvious changes
made as part of this patch:
- some of the gFoo style getters in Blocklist.jsm were only used by the XML
version of the blocklist; I've removed them and tried to remove spurious
settings of those properties in the remaining tests.
- some utility methods (e.g. distribution information getters) were also only
used for the XML version (for the update URL).
- it's no longer necessary to test switching implementations.
- in browser/base/content/test/plugins/, we ran some tests from two manifests
in order to run them with both blocklist backends. The simplest way of
reducing this back down to one was to remove the remote-settings one. If I'd
been more future-oriented when I created the duplication, perhaps I would
have moved the XML version out into a different manifest instead, but I
didn't, so now it looks like we're removing the modern one, whereas really
we're going to be running the modern one as part of the "normal" tests and
we're no longer running the "old" tests.
- removed all mentions I could see of extensions.blocklist.url which is no
longer used for anything.
- per https://bugzilla.mozilla.org/show_bug.cgi?id=1016555#c23, updated
references for the OneCRL timing and how it relates to blocklist updates.
Differential Revision: https://phabricator.services.mozilla.com/D64933
--HG--
extra : moz-landing-system : lando
As media session is an webidl interface controlled by the value of the pref `dom.media.mediasession.enabled`, and I found that in some situation (in mochitest), we can't get that interface even if the pref has been enabled.
I guess it might be related with the order of initialization of DOM objects, which might involve too much DOM details. So I'm going to take the simplest workaround, which is to enable this pref on testing environment, that can ensure that we always get the media session interface.
Differential Revision: https://phabricator.services.mozilla.com/D60785
--HG--
extra : moz-landing-system : lando
Legacy extensions are no longer loaded, so we can drop the build config for it. We
still need flags for handling experimental APIs since what we require differs between builds
and distributions.
Differential Revision: https://phabricator.services.mozilla.com/D57413
--HG--
extra : moz-landing-system : lando
Historically, mochitest and geckoview-junit tests have used the same profile.
This patch splits out a separate profile type for geckoview-junit, with exactly
the same content for now; the geckoview team can follow-up with whatever
profile changes are required for junit.
Differential Revision: https://phabricator.services.mozilla.com/D59775
--HG--
extra : moz-landing-system : lando
`media.geckoview.autoplay.request` is used to control whether we send the play request.
`media.geckoview.autoplay.request.testing` is used to control the request result in testing.
Differential Revision: https://phabricator.services.mozilla.com/D52605
--HG--
extra : moz-landing-system : lando
`media.geckoview.autoplay.request` is used to control whether we send the play request.
`media.geckoview.autoplay.request.testing` is used to control the request result in testing.
Differential Revision: https://phabricator.services.mozilla.com/D52605
--HG--
extra : moz-landing-system : lando
This turns off the telemetry to Tiles in m-c. Activity Stream related telemetry to Tiles will be handled separately.
Differential Revision: https://phabricator.services.mozilla.com/D53875
--HG--
extra : moz-landing-system : lando
The JS debugging option javascript.options.asyncstack lowers performance results and also appears to introduce noise into the tests.
Since it's disabled in release builds this change disables it in the raptor performance tests.
Differential Revision: https://phabricator.services.mozilla.com/D53335
--HG--
extra : moz-landing-system : lando
There's no effort to disable it any time soon, so I don't think it's useful to
keep the pref around.
Differential Revision: https://phabricator.services.mozilla.com/D49507
--HG--
extra : moz-landing-system : lando
There is a duplicate setting for a pref in raptor's user.js file. This patch removes the duplicate.
Differential Revision: https://phabricator.services.mozilla.com/D48204
--HG--
extra : moz-landing-system : lando
This patch adds fullscreen and windowed youtube tests for the V9 and H264 encoding at 1080p30 and 1080p60. Each subtest runs for 20 page cycles which amounts to about 5 minutes each. It also begins adding these to power test tasks running on the macosx-1014 reference hardware.
Differential Revision: https://phabricator.services.mozilla.com/D45067
--HG--
extra : moz-landing-system : lando
This pref is required by the common animation interpolation test function used
in many of the CSS test suites but currently we only enable it on Nightly. As a
result, each time a new spec adds animation tests, we get failures on our beta
simulations. Rather than turn this on for each directory it is used in each
time a new failure occurs, this patch makes us set it globally.
This patch also removes a number of instances where we set this pref locally.
It only removes the instances that were specifically added due to the
introduction of the common CSS interpolation test function. The existing
instances remain untouched since they serve as documentation of other places
where we are specifically testing that feature.
Differential Revision: https://phabricator.services.mozilla.com/D47034
--HG--
extra : moz-landing-system : lando
Add new preference `extensions.webextensions.warnings-as-errors` that
defaults to `true` in tests. Tests that expect warnings are modified
to briefly flip the pref for the specific part of the test that needs
an exception.
As part of the refactor, log entries for schema entries that contain
`"onError": "warn"` will now be prefixed by "Warning" instead of
"Error", to be consistent with the change from bug 1495908.
Differential Revision: https://phabricator.services.mozilla.com/D40548
--HG--
extra : moz-landing-system : lando
Add new preference `extensions.webextensions.warnings-as-errors` that
defaults to `true` in tests. Tests that expect warnings are modified
to briefly flip the pref for the specific part of the test that needs
an exception.
As part of the refactor, log entries forschema entries that contain
`"onError": "warn"` will now be prefixed by "Warning" instead of
"Error", to be consistent with the change from bug 1495908.
Differential Revision: https://phabricator.services.mozilla.com/D40548
--HG--
extra : moz-landing-system : lando
Hooks up slow script reporting to the ContentDelegate. Allowing slow script prompts to be implemented.
Differential Revision: https://phabricator.services.mozilla.com/D41970
--HG--
extra : moz-landing-system : lando
My previous attempt updated the wrong test profile, which does not apply to xpcshell tests.
This applies the pref override to xpcshell tests only, the only place we need it.
Differential Revision: https://phabricator.services.mozilla.com/D42865
--HG--
extra : moz-landing-system : lando
Also, remove an old obsolete preference (getWithPerformance) from test profiles.
Differential Revision: https://phabricator.services.mozilla.com/D40623
--HG--
extra : moz-landing-system : lando
This pref defaults to true, but geckoview builds set it to false. Several tests assume
this pref is set; some android xpcshell tests currently fail when run against the geckoview apk
for this reason. Setting the pref in the test profile means that geckoview tests will run
with a different pref value than geckoview would normally use, but aligns the geckoview
test environment with firefox. (An alternative would be to skip geckoview tests that rely
on the pref.)
Differential Revision: https://phabricator.services.mozilla.com/D38585
--HG--
extra : moz-landing-system : lando
This provides a set of promises that the searchservice resolves once the search engine has been configured
Differential Revision: https://phabricator.services.mozilla.com/D33660
--HG--
extra : moz-landing-system : lando
This provides a set of promises that the searchservice resolves once the search engine has been configured
Differential Revision: https://phabricator.services.mozilla.com/D33660
--HG--
extra : moz-landing-system : lando
This provides a set of promises that the searchservice resolves once the search engine has been configured
Differential Revision: https://phabricator.services.mozilla.com/D33660
--HG--
extra : moz-landing-system : lando
(The pref is about to be removed, but even before its removal, it defaults to
'true' so these tests don't need to bother setting/checking it.)
Differential Revision: https://phabricator.services.mozilla.com/D33805
--HG--
extra : moz-landing-system : lando
Razvan Maries
Andrew Osmond
Geoff Brown
alwu
Dorel Luca
Marco Bonardo
Florian Quèze
Kristján Oddsson
Dale Harvey
Bogdan Tara
Liang-Heng Chen
jayati
Daniel Holbert
Tarek Ziadé
Agi Sferro
Florin Strugariu
Narcis Beleuzu
Gijs Kruitbosch
Andrea Marchesini
Arthur Iakab
Noemi Erli
Andreea Pavel
Mike de Boer
Ciure Andrei
Andrei Oprea
Cosmin Sabou
Shane Caraveo
Masatoshi Kimura
Rob Wood
David Burns
Nan Jiang
Andrew Creskey
Emilio Cobos Álvarez
Xidorn Quan
Jonathan Kingston
Oana Pop Rus
Gregory Mierzwinski
Brian Birtles
Stephen Donner
Dylan Roeh
Rob Wu
Gurzau Raul
Elliot Stirling
Ed Lee
L. David Baron
Andrew Swan
Brindusan Cristian
Mathieu Leplatre
Mark Striemer