Closed Bug 1446017 Opened 7 years ago Closed 7 years ago

uBlock Origin unable to be disabled on pages in Nightly 61 2018-03-15 Build

Categories

(WebExtensions :: General, defect)

61 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1445537

People

(Reporter: nils, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0 Build ID: 20180315100042 Steps to reproduce: When browsing to any page that requires an ad-blocker be disabled, I'm unable to change the state of uBlock to disabled for that domain. I'm running uBlock Origin 1.15.10. It is working on the 60 branch (dev edition), and can't re-produce it on that version. Actual results: uBlock state does not change after clicking the blue 'Power Button' in the add-on. You can click on it, it turns gray, but as soon as you remove focus from the add-on pop up window, and then click the uBlock icon again, it goes back to blue or enabled. The uBlock icon also stays red indicating that it's still enabled. Expected results: 'Power Button' should've gone gray, and stayed gray, and been disabled for the page/domain that was currently being viewed.
I have the exact same problem in Linux with the latest nightly version installed.
Blocking and unblocking certain websites with it doesn't work as well so I guess if the power button doesn't work to disable it the possibility to unblock and/or to block would also be affected. It was working fine about a week and a half ago. Possible regression?
Mine was a fresh install as of yesterday, and I refreshed the profile, so basically it was a clean install of the Add-On and a fresh Firefox profile. Not sure if it was working yesterday as I didn't attempt to unblock anything.
Flags: needinfo?(rhill)
I see it has been fixed in today's build.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Component: Untriaged → WebExtensions: General
Product: Firefox → Toolkit
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.