Skip to content
This repository was archived by the owner on Dec 11, 2019. It is now read-only.

Turn off shields on about:safebrowsing shows about:error page instead of loading the actual site and shields become inactive #9441

Closed
srirambv opened this issue Jun 14, 2017 · 5 comments

Comments

@srirambv
Copy link
Collaborator

  • Did you search for similar issues before submitting this one?
    Yes

  • Describe the issue you encountered:
    Turn off shields on about:safebrowsing shows about:error page instead of loading the actual site and shields become inactive

  • Platform (Win7, 8, 10? macOS? Linux distro?):
    Windows 10 x64

  • Brave Version (revision SHA):
    Brave 0.17.1
    rev 84dbc8e
    Muon 4.0.3

  • Steps to reproduce:

    1. Clean install 0.17.1
    2. Visit http://downloadme.org, ensure about:safebrowsing#http://downloadme.org/ window is shown
    3. Disable Shields, about:error page is shown, but URL is still showing about:safebrowsing#http://downloadme.org/, Due to about:error shields menu is disabled
    4. Open a new page in the previous tab or a new tab, shields for that page is opened
  • Actual result:
    Turn off shields on about:safebrowsing shows about:error page instead of loading the actual site and shields become inactive

  • Expected result:
    Should just load the site and not about:error when shields is turned off

  • Will the steps above reproduce in a fresh profile? If not what other info can be added?
    Yes

  • Is this an issue in the currently released version?
    No

  • Can this issue be consistently reproduced?
    Yes

  • Extra QA steps:
    1.
    2.
    3.

  • Screenshot if needed:
    safebrowsing

  • Any related issues:
    cc: @diracdeltas

@diracdeltas
Copy link
Member

note that this works on master

@diracdeltas
Copy link
Member

it shows about:error because downloadme.org doesn't exist anymore, not because of Brave

@bbondy
Copy link
Member

bbondy commented Jun 21, 2017

Moving to 0.18.x, lmk if that's a problem @diracdeltas thx.

@bbondy bbondy modified the milestones: 0.18.x (Developer Channel), 0.17.x (Beta Channel) Jun 21, 2017
@luixxiul
Copy link
Contributor

I think we would display then 404 error page.

@bbondy
Copy link
Member

bbondy commented Jun 21, 2017

should be working in 0.18.x so marking as closed in this milestone.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.