Closed Bug 1005108 Opened 11 years ago Closed 11 years ago

OS X nightly: click on ghostery button makes all but one menu unclickable

Categories

(Firefox :: Untriaged, defect)

32 Branch
x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: clements, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:32.0) Gecko/20100101 Firefox/32.0 (Beta/Release) Build ID: 20140502030202 Steps to reproduce: - start OS X Firefox Nightly (32.0a1 (2014-05-02)) with ghostery 5.2.1 installed - click on ghostery icon, see box open as expected - click outside box to make box disappear - now, click and hold on "History" menu (for example) Actual results: - history menu does not appear. None of the menus appear when clicked, *except* the "apple" and "Nightly" menus in the top left corner. Expected results: Menu should have appeared under "History" label. Problem can be resolved by quitting and restarting firefox. In general, it seems to me that this is not something that an add-on should be able to do, which is why I'm submitting this as a Firefox bug rather than a Ghostery bug.
This is still likely to be a ghostery issue. See also bug 1005050. Are there any errors in the browser console when this happens?
Flags: needinfo?(clements)
I'm assuming you're referring to the '-jsconsole' cmd-line arg? I ran again with this enabled. On clicking the ghostery button, I got these two lines: - value is not a non-null object browser.js:14799 - docShell.QueryInterface(...).sessionHistory is null content-sessionStore.js:228 On dismissing the window, I got this message: - Empty string passed to getElementById(). Does this confirm your suspicion that this is a ghostery bug? Many thanks for your fast response!
Flags: needinfo?(clements)
Yes, I see related bugs on Ghostery's website. I'm closing this bug report. Thanks for your help!
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
(In reply to clements from comment #3) > Yes, I see related bugs on Ghostery's website. I'm closing this bug report. > Thanks for your help! Welcome! Thanks for helping to track this one down. :-)
You need to log in before you can comment on or make changes to this bug.