Open
Bug 1349774
Opened 7 years ago
Updated 1 year ago
Safe browsing notification bar is only shown once when a warning is ignored
Categories
(Toolkit :: Safe Browsing, defect, P5)
Tracking
()
People
(Reporter: jkt, Unassigned)
Details
STR: 1. Go to https://www.itisatrap.org/firefox/its-an-attack.html 2. Click ignore this message 3. See the top bar issue Bug 1347493 4. Click [Get me out of here] in the top bar 5. Press back Expected outcome: User to be shown warning bar or the full page warning. Actual outcome: User is shown no warning and there isn't an issue reported on the page, all subsequent navigations to this page appear normal even in different tabs. Closing the browser and reopening shows the warning again.
Updated•7 years ago
|
Priority: -- → P5
Summary: Safe browsing warning can be bypassed → Safe browsing notification bar is only shown once when a warning is ignored
Comment 1•6 years ago
|
||
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
Updated•6 years ago
|
Status: RESOLVED → REOPENED
Resolution: INACTIVE → ---
Updated•2 years ago
|
Severity: normal → S3
Comment 2•1 year ago
|
||
This Issue is still reproduced on MacOS 12, Win 11 and Ubuntu 22.04 with Fx versions: 102.11.0esr, 113.0, 114.0b3, and latest Nightly 115.0a1 (2023-05-11) following these steps:
- Go to https://www.itisatrap.org/firefox/its-an-attack.html
- Click on “See details”
- Click on “ignore the risk”
- Click on “Get me out of here!” in the top bar
- Press the “Go back one page” button (or Cmd/Ctrl+LeftArrow)
Additional notes:
Possibly related issue: bug 1572243.
Has STR: --- → yes
status-firefox113:
--- → affected
status-firefox114:
--- → affected
status-firefox115:
--- → affected
status-firefox-esr102:
--- → affected
OS: Linux → All
Hardware: x86_64 → Desktop
Version: 51 Branch → Trunk
You need to log in
before you can comment on or make changes to this bug.
Description
•