-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Popup/popunder blocking broken after opening uBO's dashboard through popup panel #3057
Comments
Hmm, I'm wondering why you do |
@kasper93 I don't know, I didn't put this code there: b301ac0#diff-bc664f26b9c453e0d43a9379e8135c6a. It didn't occur to me to try |
@gorhill: Sure, I just read here https://developer.mozilla.org/en-US/Add-ons/WebExtensions/user_interface/Popups
So it seems to be blessed way to close popups. Might be hard to remember why you did this way after all this time. :) |
@kasper93, you're right, I confirm this works fine. Wish I had seen your comment before pushing rc2. I removed my comment re "sticky" above to avoid any confusion. |
I removed the "browser bug" label, but I do wonder what is occurring internally for Firefox API's |
|
Putting back the "browser bug" label, this simple HTML document will cause
|
Thanks for the debugging @gorhill and others. I have poked a bit more at it, created a test case and reported the bug at: https://bugzilla.mozilla.org/show_bug.cgi?id=1403349 |
First reported here by @kasper93.
This is unrelated to the regression, which was fixed.
This affects all versions of Firefox, including in Nightly.
The repro steps are quite simple (from my end, both with Firefox 55 and Nightly):
webNavigation.onCreatedNavigationTarget
to properly set thesourceTabId
property.about:addons
.Result: uBO fails to properly filter the popup.
After much investigation, it turns out that the one call to
vAPI.closePopup()
invapi-common.js
is causing this issue:The issue does not exist with Chromium, with the same code path.
I have no idea why this happens. It appears Firefox's internals are in a bad state after step 4: the
sourceTabId
fromwebNavigation.onCreatedNavigationTarget
is always-1
.The text was updated successfully, but these errors were encountered: