- Renames deleteDataFromBaseDomain to deleteDataFromSite.
- Cleans up terminology for (schemeless site) to better align with standards.
- deleteDataFromSite requires a schemeless site to be passed in. We will no longer
implicitly convert the host to a site.
- Removes the host fallback for SiteDataManager and ForgetAboutSite. The new schemeless site
helper Services.eTLD.getSchemelessSiteFromHost accounts for this.
Differential Revision: https://phabricator.services.mozilla.com/D220605
- Renames deleteDataFromBaseDomain to deleteDataFromSite.
- Cleans up terminology for (schemeless site) to better align with standards.
- deleteDataFromSite requires a schemeless site to be passed in. We will no longer
implicitly convert the host to a site.
- Removes the host fallback for SiteDataManager and ForgetAboutSite. The new schemeless site
helper Services.eTLD.getSchemelessSiteFromHost accounts for this.
Differential Revision: https://phabricator.services.mozilla.com/D220605
- Renames deleteDataFromBaseDomain to deleteDataFromSite.
- Cleans up terminology for (schemeless site) to better align with standards.
- deleteDataFromSite requires a schemeless site to be passed in. We will no longer
implicitly convert the host to a site.
- Removes the host fallback for SiteDataManager and ForgetAboutSite. The new schemeless site
helper Services.eTLD.getSchemelessSiteFromHost accounts for this.
Differential Revision: https://phabricator.services.mozilla.com/D220605
Other than in one test, we don't use it separate from CLEAR_HISTORY.
They are two different bits because in the past one bit could only have
one cleaner associated to it, but that is no longer an issue.
Differential Revision: https://phabricator.services.mozilla.com/D222107
- Renames deleteDataFromBaseDomain to deleteDataFromSite.
- Cleans up terminology for (schemeless site) to better align with standards.
- deleteDataFromSite requires a schemeless site to be passed in. We will no longer
implicitly convert the host to a site.
- Removes the host fallback for SiteDataManager and ForgetAboutSite. The new schemeless site
helper Services.eTLD.getSchemelessSiteFromHost accounts for this.
Differential Revision: https://phabricator.services.mozilla.com/D220605
This was regressed/missed in bug 1910698, cought by ts check in
extensions code, and I also fixed a couple other places.
Differential Revision: https://phabricator.services.mozilla.com/D218504
This was regressed/missed in bug 1910698, cought by ts check in
extensions code, and I also fixed a couple other places.
Differential Revision: https://phabricator.services.mozilla.com/D218504
This was regressed/missed in bug 1910698, cought by ts check in
extensions code, and I also fixed a couple other places.
Depends on D218503
Differential Revision: https://phabricator.services.mozilla.com/D218504
When contextmenu event is fired by mouse and the selection of active element
isn't collapsed, we should show action menu instead of context menu.
Actually, action menu depends on accessible caret event, so I emulate this
event to handle action menu. Also, focus or selection for active element is
changed, action menu should be dismissed.
Desktop's Gecko uses some JavaScript modules for handling context menu, so
we also use it.
Differential Revision: https://phabricator.services.mozilla.com/D217823
Given meta/ctrl key should use browser.tabs.loadInBackground pref instead of
browser.tabs.loadDivertedInBackground pref, the existing
nsIBrowserDOMWindow.OPEN_NEWTAB behavior doesn't match the requirement.
Add dedicate flag for "open in foreground tab" to make it controllable from
nsWindowWatcher::IsWindowOpenLocationModified.
Differential Revision: https://phabricator.services.mozilla.com/D201929
The patch includes the following changes:
1. Implements a workaround for a test failure (Bug 1905040). This issue occurs because,
in the current architecture, the child process calls markAsAutoCompletableField regardless of
whether the field is in a valid section.
2. `profile` is now stored in `fillMessageData`. Accordingly, updates where we use `profile` in
`GeckoViewAutocomplete.sys.mjs`.
3. Autofill is triggered from the parent process, so the autofillFields API is called directly
instead of sending a `FormAutofill:FillForm` message to the child process.
Differential Revision: https://phabricator.services.mozilla.com/D215078
On non-supported translation language locales, the translations download screen
should behave like the pivot locale, because the pivot language is the fallback.
However, GeckoView is sending an "English" language packet in the non-supported
translation case. It should not send an English language model, because it is
inoperable and implicit in this case as the fallback.
Differential Revision: https://phabricator.services.mozilla.com/D215391
When translating to a language not English, the translation runs through a pivot language.
For example, when translating a page from Spanish to German, Spanish to English and
English to German are downloaded.
Before this patch, the pivot language was always accounted for in the download size.
However, once the pivot is downloaded, then it doesn't need to be accounted for in other models.
This patch updates to only counts the pivot, if the pivot is not downloaded. Once the pivot is downloaded,
then the size is not counted in the model size.
Differential Revision: https://phabricator.services.mozilla.com/D214637
The code path that was used for loading a document
with fission disabled did not take user activation into account.
This made almost all WPTs for Text Fragments fail,
since they depend on this flag to decide if
a text directive is allowed to be scrolled to.
This patch makes sure that the user activation is
also available for code paths that run through
`CanonicalBrowsingContext::FixupAndLoadURIString()`
to load a document.
This is done by adding a flag `hasValidUserGestureActivation`
to the `nsIOpenWindowInfo`, which carries it through
the JS stack for loading a document.
Differential Revision: https://phabricator.services.mozilla.com/D213401
Before this patch, GeckoViewTranslations was sending `undefined` to
`translate` for the parameter `reportAsAutoTranslate`. This was
causing `NULL` in the extra on the packet, instead of the expected value.
Differential Revision: https://phabricator.services.mozilla.com/D214769
The code path that was used for loading a document
with fission disabled did not take user activation into account.
This made almost all WPTs for Text Fragments fail,
since they depend on this flag to decide if
a text directive is allowed to be scrolled to.
This patch makes sure that the user activation is
also available for code paths that run through
`CanonicalBrowsingContext::FixupAndLoadURIString()`
to load a document.
This is done by adding a flag `hasValidUserGestureActivation`
to the `nsIOpenWindowInfo`, which carries it through
the JS stack for loading a document.
Differential Revision: https://phabricator.services.mozilla.com/D213401
