1578686 - When attempting to set set a blocked page as homepage, some kind of error should be displayed

Status: NEW

(Firefox :: New Tab Page, defect, P3)

Description

[Daniel Bodea [:danibodea]]

Note

• When the user attempts to set a blocked URL as homepage, there should be some way to notify the user that he is unable to do so.

Affected versions

• Nightly v71.0a1
• Beta v70.0b3

Affected platforms

• All

Steps to reproduce

1. Open browser.
2. Install the "remote-settings-devtools" extension on the browser.
3. Click the "Remote Settings Devtools" extension icon from the toolbar.
4. Change the Environment setting (from top-right corner) to Stage.
5. Click on "Clear ALL local data" button.
6. Click on the "Poll Server" button (or Click on the "Force Sync" button from the "main/hijack-blocklists" Collection.
7. In a tab open "https://www.ecosia.org/search?q=search+result+page" (currently blocked). Close all other tabs.
8. Open the browser's options page, Home tab.
9. Click on "Homepage and new windows" drop-down, and select "Custom URLs..." option.
10. Click the "Use current pages" button.

Expected result

• Some kind of error should be displayed, notifying the user that he is unable to use that URL as a homepage.

Actual result

• Nothing happens. Homepage is not set; error not displayed.

Comment 1

[Jessilyn Davis]

Nan - is this related to the search hijacking work that UJet was working on this year? Did it just land in Beta?

Comment 2

[Nan Jiang [:nanj]]

See my comment for bug 1578685.

Comment 3

[Jessilyn Davis]

:standard8 - this is another one related to bug 1578685 - can you advise on next steps here?

Comment 4

[Mark Banner (:standard8)]

We should do this, though it doesn't need to ship with the initial implementation - so P2? I can probably pick it up once we have UX.

Need-info to Michael: Please can you supply some UX for the error we should display to the user.

Comment 5

[Mark Banner (:standard8)]

Hopefully users won't generally be doing otherwise, so probably P3 for now.