This also adds `GeckoView.setAutofillEnabled()`, which is enabled by
default. Apps can disable this if they don't want to use the Android
autofill service. This will allow them to set their own
`AutofillDelegate` on the `GeckoSession` and provide their own
autofill implementation.
Differential Revision: https://phabricator.services.mozilla.com/D47483
--HG--
extra : moz-landing-system : lando
This is an alternative to `GeckoSession.provideAutofillVirtualStructure()`
that does not rely on the `ViewStructure` class. This is necessary to
support autofill functionality on older devices or without involving
the Android autofill service.
This patch also moves the existing autofill tests into
AutofillDelegateTest.kt and converts them to use this new API
instead of the `ViewStructure` one. This allows us to test on devices
lower than SDK 26 (which includes automation). In addition to the API
changes, some tests also needed some greening up.
Differential Revision: https://phabricator.services.mozilla.com/D47482
--HG--
extra : moz-landing-system : lando
This also moves `autofill()` and `provideAutofillVirtualStructure()`
into `GeckoSession`.
Differential Revision: https://phabricator.services.mozilla.com/D47481
--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
During path building, mozilla::pkix filters out candidate certificates provided
by trust domains where the subject distinguished name does not match the issuer
distinguished name of the certificate it's trying to find an issuer for.
However, if there's a problem decoding the candidate issuer certificate,
mozilla::pkix will make a note of this error, regardless of if that certificate
was potentially a suitable issuer. If no trusted path is found, the error from
that unrelated certificate may ultimately be returned by mozilla::pkix,
resulting in confusion.
Before this patch, NSSCertDBTrustDomain could cause this behavior by blithely
passing every known 3rd party certificate to mozilla::pkix (other sources of
certificates already filter on subject distinguished name). This patch adds
filtering to 3rd party certificates as well.
Differential Revision: https://phabricator.services.mozilla.com/D48120
--HG--
extra : moz-landing-system : lando
This is a partial cherrypick of https://webrtc.googlesource.com/src/+/f89110d67902e787f6745ad2b52f7f09fc808512.
The cropping changes in that revision are problematic on our version of webrtc.org and
result in distorted video, which looks as though there is a stride problem. This takes
the change to try to use PW_RENDERFULLCONTENT and to fall back to the current code if
that fails. This fixes capturing Chrome windows and allows Firefox to properly capture
its own window.
Using PW_RENDERFULLCONTENT can adversely affect performance. Using the
CroppingWindowCapturer can avoid using the WindowCapturer in some circumstances and so
result in better performance. Bug 1586071 tracks switching to the
CroppingWindowCapturer.
Differential Revision: https://phabricator.services.mozilla.com/D48108
--HG--
extra : moz-landing-system : lando
This should fix the doc builds on Windows, as sphinx-js added Windows support in 2.3.1 and 2.4. We also now get support for variadic args, @deprecated, and @see, along with other features.
sphinx-js 2.7.1 changed the default cwd to be the one containing conf.py, so I also had to twiddle `jsdoc_config_path`.
Let some other pipenv pinnings update themselves as well, as, if I don't, they'll just update themselves the next time somebody runs `mach doc`, dirtying their tree.
I suspect this also fixes bug 1556460, whose equivalent bug in sphinx-js is https://github.com/mozilla/sphinx-js/issues/106. IOW, it should no longer break with versions of jsdoc >= 3.6.
Differential Revision: https://phabricator.services.mozilla.com/D48122
--HG--
extra : moz-landing-system : lando
The changes are just cleanup for member variables/methods that should
be private to ServiceWorkerManager.
Depends on D48179
Differential Revision: https://phabricator.services.mozilla.com/D48181
--HG--
extra : moz-landing-system : lando
Also replace ServiceWorkerManager shutdown logic's normal for-loops with
range-based for-loops.
Depends on D43170
Differential Revision: https://phabricator.services.mozilla.com/D48179
--HG--
extra : moz-landing-system : lando
Due to limitations in the test harness, the "serviceworker_e10s" (for mochitest
and xpcshell) and "sw-e10s" (for WPT) values will match mozinfo's "nightly_build"
value, unless overridden by "--setpref dom.serviceWorkers.parent_intercept=..."
provided at the CLI.
Differential Revision: https://phabricator.services.mozilla.com/D43170
--HG--
extra : moz-landing-system : lando
- Listen for observer topics in the parent-process when in parent intercept mode
- Remove an extra postMessage call (and the corresponding message handler)
Differential Revision: https://phabricator.services.mozilla.com/D44513
--HG--
extra : moz-landing-system : lando
Environment should be bytes on Python 2 (to avoid Windows errors) and text on
Python 3. The 'ensure_subprocess' env utility function handles this.
Differential Revision: https://phabricator.services.mozilla.com/D48115
--HG--
extra : moz-landing-system : lando
Because it's possible to have the IPC fail when checking if MediaKeySystemAccess
should be allowed, we should gracefully handle the IPC failure case. If we don't
gracefully handle here, closing the tab during requestMediaKeySystemAccess can
result in crashing the content process.
Differential Revision: https://phabricator.services.mozilla.com/D48116
--HG--
extra : moz-landing-system : lando
Allow access to extra services needed to open file pickers from the Flash process on 10.15.
Differential Revision: https://phabricator.services.mozilla.com/D48145
--HG--
extra : moz-landing-system : lando
Use test1.mochi.test:8888 instead of example.org so that the innermost iframe is
still same-compartment with the top-level page.
Differential Revision: https://phabricator.services.mozilla.com/D48192
--HG--
extra : moz-landing-system : lando
Bug 1584244 fixed some of the issue for getters,
but not all of them.
Instead of trying to unescape the node name, we
put the actual property name into the node, so
we can reuse it later.
Differential Revision: https://phabricator.services.mozilla.com/D47876
--HG--
extra : moz-landing-system : lando
This removes support for 'passive' and makes our element and data segment
syntax follow standard syntax much more closely.
Element segments now require either 'func' or 'funcref' in the right
position, and require a table index for active segments that don't use
the designated MVP shorthand.
Data segments require an offset when there's a memory index present.
Also add support for the noise syntax (offset x) for the
initialization offset in active segments.
I did not add support for the variant of in-line elements in the table
definition that allows the starting offset to be specified; this is
followup work.
Also tidy up some naming and comments in an attempt to clarify the
flow in the encoder.
Differential Revision: https://phabricator.services.mozilla.com/D48031
--HG--
extra : moz-landing-system : lando
