Open Bug 1833828 Opened 1 year ago Updated 10 months ago

The Always Continue button from the DOH Fallback Warning page should let the users know that it disables the Warning page for all other websites

Categories

(Core :: Networking: DNS, enhancement, P2)

Desktop
All
enhancement

Tracking

()

People

(Reporter: rdoghi, Unassigned)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [necko-triaged])

Found in

  • Nightly 115.0a1 (2023-05-18)

Affected versions

  • Nightly 115.0a1 (2023-05-18)

Affected platforms

  • ALL

Preconditions:
Add nothing.test to the Custom Providers for Increased Protection in DOH settings.
Have network.trr_ui.show_fallback_warning_option - TRUE in about:config
Check/Enable the "Warn if a third party actively prevents secure DNS" in DOH settings.

Steps to reproduce

  1. Reach best.test.
  2. Hover over the Always continue.
  3. Click the Always Continue button.

Expected result

  • We should show a bit of extra information when either hovering over the "Always continue" button or around the the "Always continue" button to let the users know that clicking that button will automatically disable the Fallback warning page for all other websites.
    We could show something on hover or underneath the button like: "Never show this Warning page again." / "This will disable the Warning page for all other websites." / "The Always continue button will disable the warning page from DOH settings and it can only be enabled again from DOH Settings."

Actual result

  • The Always continue will disable the warning page completely, users might want to disable the Warning page for that specific website and they might not realise that it completely disables it for all other websites.
    Compared to the Max Protection mode where the button is "Always continue for this site" where this will add an exception for that specific website the "Always continue" button from the Increased Protection mode will completely disable the warning page.

Regression range
N/A

:rdoghi, if you think that's a regression, could you try to find a regression range using for example mozregression?

Its just a suggestion, there's no need for a regression range.

Priority: -- → P2
Whiteboard: [necko-triaged]
You need to log in before you can comment on or make changes to this bug.