Opened on 11/07/2017 at 07:16:08 PM
Closed on 11/08/2017 at 03:52:33 PM
#6002 closed defect (invalid)
About:Blank does not clear page
Reported by: | traynard | Assignee: | |
---|---|---|---|
Priority: | Unknown | Milestone: | |
Module: | Platform | Keywords: | |
Cc: | mapx, trev, sebastian, manish | Blocked By: | |
Blocking: | Platform: | Firefox | |
Ready: | no | Confidential: | no |
Tester: | Unknown | Verified working: | no |
Review URL(s): |
Description
Environment
Firefox with ABP 3.0
How to reproduce
Ensure ABP is enabled
- Navigate to any website
- In address bar, remove current URL and enter "About:blank" and submit
Observed behaviour
The address bar is cleared and user can no longer interact with webpage (other than scrolling) but the page is not cleared or "blank" as expected until tabs are switched.
Expected behaviour
after navigating to about:blank, page should be fully cleared.
NOTE: This works fine when ABP is not installed.
Attachments (0)
Change History (8)
comment:1 Changed on 11/07/2017 at 07:20:22 PM by traynard
comment:2 Changed on 11/07/2017 at 11:00:50 PM by mapx
- Cc mapx trev added
comment:3 Changed on 11/07/2017 at 11:02:19 PM by mapx
error in browser console:
Failed to execute ‘postMessage’ on ‘DOMWindow’: The target origin provided (‘https://www.google.it’) does not match the recipient window’s origin (‘null’).
I can reproduce the issue in FF 56 but not in FF 57
comment:4 Changed on 11/08/2017 at 10:07:52 AM by trev
- Cc sebastian manish added
- Component changed from Adblock-Plus-for-Firefox to Platform
I can also reproduce in Firefox 56. No error message in my case - this error seems to be caused by the particular website and unrelated. This is some kind of Firefox bug, need to be narrowed down.
comment:5 Changed on 11/08/2017 at 01:43:06 PM by mapx
firefox bug (courtesy of gorhill https://github.com/gorhill/uBlock/issues/1930#issuecomment-342818986):
comment:6 Changed on 11/08/2017 at 02:25:51 PM by trev
The only strange thing: gorhill filed that bug for Firefox 58, yet I cannot reproduce it with this Firefox version. But if his analysis is correct, we cannot really avoid hitting this bug.
comment:7 Changed on 11/08/2017 at 03:40:19 PM by mapx
Yeah, he corrected himself, it's about the same buggy FF 56.
comment:8 Changed on 11/08/2017 at 03:52:33 PM by trev
- Resolution set to invalid
- Status changed from new to closed
Then I wonder why he even bothered reporting the bug. It's not like anybody will bother backporting the fix to Firefox 56. If it's fixed in Firefox 57 then all we need to do is wait a week for Firefox 57 to become the current stable release.
Resolving as "invalid" meaning: not our bug and no way of fixing this on our end.
Video example (file was too large to attach): https://drive.google.com/a/adblockplus.org/file/d/17Gi0UKmt8hd3_PBV6-bzDQ3Pkof4aQam/view?usp=sharing