This patch moves the addons-search-detection system add-on in tree and
adjusts the build configuration to make it a built-in add-on (which
requires changes in the `BrowserGlue.jsm` file).
Summary of the changes made to the different files:
- `api.js`: added license header, reformatted with Prettier, then fixed
ESLint errors: use of `Services.eTLD` instead of
`XPCOMUtils.defineLazyServiceGetter(...)` and defined
`"searchInitialized"` on `this` instead of `global` which was unknown
- `background.js`: added license header, reformatted with Prettier,
removed debug logs because they were off by default anyway, fixed
ESLint error: id => addonId because addonId was already defined in a
parent scope
- `manifest.json`: version number changed + `hidden: true`
- `schema.json`: no change await addon.enable();
Differential Revision: https://phabricator.services.mozilla.com/D128908
This patch moves the addons-search-detection system add-on in tree and
adjusts the build configuration to make it a built-in add-on (which
requires changes in the `BrowserGlue.jsm` file).
Summary of the changes made to the different files:
- `api.js`: added license header, reformatted with Prettier, then fixed
ESLint errors: use of `Services.eTLD` instead of
`XPCOMUtils.defineLazyServiceGetter(...)` and defined
`"searchInitialized"` on `this` instead of `global` which was unknown
- `background.js`: added license header, reformatted with Prettier,
removed debug logs because they were off by default anyway, fixed
ESLint error: id => addonId because addonId was already defined in a
parent scope
- `manifest.json`: version number changed + `hidden: true`
- `schema.json`: no change await addon.enable();
Differential Revision: https://phabricator.services.mozilla.com/D128908
This patch contains the following changes:
- Moved the files from https://github.com/mozilla-extensions/proxy-monitor (`extension/*`) to `browser/extensions/proxy-failover`.
- In `api.js`:
- Added license at the top of the file
- Added a `globals` comment to tell ESLint about `ExtensionAPI`
- Added a comment to disable an ESLint rule on L289 (consistent-return)
- Added a comment to disable an ESLint rule on L422 (no-unused-vars)
- Reformatted some comment blocks to break ato break at ~80 chars
- Added `moz.build` to build the `proxy-failover` extension
- Added `proxy-failover` to the list of built-in system add-ons
- Added a smoke test to make sure the add-on is loaded
Differential Revision: https://phabricator.services.mozilla.com/D128466
Enable the feature only in Nightly.
Add functionality for previewing and autofilling into multiple cc-number fields.
Fix test_Lush.js case.
Add logic to handle credit card saving/update when multiple cc-number fields are present.
Add heuristic test for Lufthansa site.
Add test for filling cc-number when there are multiple cc-number fields in a form.
Add test for collecting multiple cc-number fields via collectFormFields.
Add multiple cc-number fields case to onFormSubmitted test.
Add multiple cc-number fields with maxlength=4 case to markAsAutofillField.
Add implementation of the preview and fill test cases for multiple cc-number fields.
Differential Revision: https://phabricator.services.mozilla.com/D127987
These tests are excluded from android test runs in moz.build. Including
an explicit annotation in each manifest avoids scheduling confusion.
browser-chrome and plain-chrome tests in browser/ are of no concern,
since those test types are never scheduled on android.
Differential Revision: https://phabricator.services.mozilla.com/D125266
With the non-native theme we don't need filter for this to affect
"native" inputs, we can just implement the logic in nsNativeBasicTheme
instead.
A bit unfortunate that we need that special-case, but it seems better
than using filter, which can break websites due to it creating an
stacking context.
I _think_ there are tests that I need to adjust for this change, but if
not I'll write some.
Keep the current behavior behind a pref just in case.
Differential Revision: https://phabricator.services.mozilla.com/D125232
Enables autofilling into fields that may have been filled by the site.
Enables autofill preview to work as expected if a field already has a value.
Ensures autofill does not restore the default value if the user manually clears out the field's value.
This fixes the case on next.co.uk where the value of the cardholder name is being used as a placeholder.
Differential Revision: https://phabricator.services.mozilla.com/D123260
Prevent simple hidden fields from being eligible for autofill.
'Simple' in this case means fields that have the hidden attribute or 'display:none' inline property.
Differential Revision: https://phabricator.services.mozilla.com/D120669
Google Trends subframes are currently broken by dFPI protections, as they
expect the Google NID cookie to be present as per their set-cookie
response header, but it is being blocked.
This patch adds a new custom SmartBlock-style shim which:
- listens for requests made for Google Trends subframes.
- remembers their set-cookie response header.
- redirects the request right back to the same URL.
- subsequently passes along the saved cookie, preventing the breakage.
Differential Revision: https://phabricator.services.mozilla.com/D123372
