Use the Search Submission URL list to block homepages set by hijacking
Categories
(Firefox :: New Tab Page, enhancement, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox70 | --- | fixed |
People
(Reporter: nanj, Assigned: standard8)
References
(Blocks 1 open bug)
Details
User Story
Requirements: - Block any attempt to set the homepage to one that matches the (new) home page ignore list from the hijack-blocklists. - If on startup, the saved preference for the homepage is a blocked URL, then reset it to use the default homepage instead. - Note, this will probably cause the wrong homepage to be used for the window(s) created on startup until Firefox is restarted. - We will attempt to reset the homepage preference if it is invalid when the ignore list is updated. - We will record event telemetry ("homepage.preference.ignore") when the preference is reset or blocked from being set. The value parameter will be - `saved_reset` for when a saved preference is reset (e.g. initial load of the ignore list after startup, or ignore list update received). - `set_blocked_extension` for a WebExtension trying to set the preference to an ignored value via `chrome_settings_overrides` - `set_blocked` if something else tries to set the preference to an ignored value (e.g. the user via preferences, though we don't expect this to be a common case).
Attachments
(5 files)
Reporter | ||
Updated•6 years ago
|
Updated•6 years ago
|
Comment 1•6 years ago
|
||
Goal to get this in 68. The bug dependencies on this should be fixed in time. Thanks!
Updated•6 years ago
|
Updated•6 years ago
|
Assignee | ||
Comment 2•6 years ago
|
||
Adding user story based on discussions I've had.
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Comment 3•6 years ago
|
||
Can you put in a PI request so QA knows to plan to test this once it lands? Thanks!
Assignee | ||
Comment 4•6 years ago
|
||
(In reply to Liz Henry (:lizzard) (use needinfo) from comment #3)
Can you put in a PI request so QA knows to plan to test this once it lands? Thanks!
This is already covered in PI-105.
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 5•6 years ago
|
||
Note, although the submission url and home page blocklists are likely to be the same, we decided to have separate lists for the time being, in case there does need to be a difference for some reason that we haven't thought of yet.
Assignee | ||
Comment 6•6 years ago
|
||
I'm updating the user story to reflect what we've actually implemented. It was slightly easier to handle the value of the existing homepage preference with the ignore list when the ignore list gets loaded - though there's a slight compromise on the home page not being reset for the windows opened at the start of that session. Doing so, would cause extra disk and maybe network activity which would block startup.
Assignee | ||
Comment 7•6 years ago
|
||
This separates out the search ignore list handling into its own module in preparation for use elsewhere as well.
The search ignore list unit tests still largely interact with RemoteSettings to remain as integration tests.
Assignee | ||
Comment 8•6 years ago
|
||
Depends on D40391
Assignee | ||
Comment 9•6 years ago
|
||
Depends on D40392
Assignee | ||
Comment 10•6 years ago
|
||
Depends on D40393
Assignee | ||
Comment 11•6 years ago
|
||
Comment 12•6 years ago
|
||
Hey Mark,
We need this to go through to the data steward review process since we are adding telemetry. Would you be able to create a public bug describing the added collection by responding to these questions and flagging me for data-review?
-
What questions will you answer with this data?
-
Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements?
-
What alternative methods did you consider to answer these questions? Why were they not sufficient?
-
Can current instrumentation answer these questions?
-
List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories on the Mozilla wiki.
-
How long will this data be collected? Choose one of the following:
-
What populations will you measure?
-
If this data collection is default on, what is the opt-out mechanism for users?
-
Please provide a general description of how you will analyze this data.
-
Where do you intend to share the results of your analysis?
-
Is there a third-party tool (i.e. not Telemetry) that you are proposing to use for this data collection?
Assignee | ||
Comment 13•6 years ago
|
||
Mike Connor & I have agreed there's no need for this to be private. Will add the data review in a bit once patches are updated.
Assignee | ||
Comment 14•6 years ago
|
||
Assignee | ||
Comment 15•6 years ago
|
||
Updated•6 years ago
|
Updated•6 years ago
|
Assignee | ||
Comment 16•6 years ago
|
||
Comment 17•6 years ago
|
||
Updated•6 years ago
|
Updated•6 years ago
|
Comment 18•6 years ago
|
||
Comment 19•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/38b134c75aaf
https://hg.mozilla.org/mozilla-central/rev/68d8d2bf9570
https://hg.mozilla.org/mozilla-central/rev/eb1eff2ef485
https://hg.mozilla.org/mozilla-central/rev/e966b7945f69
Description
•