- 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 patch installs the framework for various platforms to inform the user of
one of two things: 1) a coming system dialog asking for system geolocation
permission that will be presented after the Firefox doorhanger asking for
permission for the page, and 2) that we will open a system preferences window,
where the user can enable geolocation for Firefox because it is currently not
enabled. The code that handles this has been remoted to the parent process
since implementations will not be able to operate in the content process
sandbox.
Here, it stubs the behavior so this does nothing on every platform.
In this patch series, the behavior will be implemented for Windows.
Note: The code will run the geolocation for the page if the user granted it in
Firefox, regardless of whether the user granted or canceled the system
permission. This respects the user's instruction and provides a work-around in
the event of a bug, although it would usually either fail to get a location or
it will get a very poor one (e.g. via IP lookup).
Differential Revision: https://phabricator.services.mozilla.com/D216473
This also changes `removeClientId` to `resetIdentifiers` and actually
generates the new identifiers. Everywhere that currently calls
`removeClientId` already immediately re-creates the client ID anyway.
Differential Revision: https://phabricator.services.mozilla.com/D219594
This moves everything except DOMUpdateBlockedPopups, where the current forwarding handler is helpful because it avoids loading
this module entirely until/unless we actually get blocked popups.
Differential Revision: https://phabricator.services.mozilla.com/D217500
This patch installs the framework for various platforms to inform the user of
one of two things: 1) a coming system dialog asking for system geolocation
permission that will be presented after the Firefox doorhanger asking for
permission for the page, and 2) that we will open a system preferences window,
where the user can enable geolocation for Firefox because it is currently not
enabled. The code that handles this has been remoted to the parent process
since implementations will not be able to operate in the content process
sandbox.
Here, it stubs the behavior so this does nothing on every platform.
In this patch series, the behavior will be implemented for Windows.
Note: The code will run the geolocation for the page if the user granted it in
Firefox, regardless of whether the user granted or canceled the system
permission. This respects the user's instruction and provides a work-around in
the event of a bug, although it would usually either fail to get a location or
it will get a very poor one (e.g. via IP lookup).
Differential Revision: https://phabricator.services.mozilla.com/D216473
This leaves out `security.insecure_connection_text.enabled` and
`security.insecure_connection_text.pbmode.enabled`, that should also be part of
ScotchBonnet, but are managed by a different component.
Differential Revision: https://phabricator.services.mozilla.com/D216181
