No visible doorhanger on add-on update

NEW
Unassigned

Status

SeaMonkey
General
6 years ago
4 years ago

People

(Reporter: tonymec, Unassigned)

Tracking

({regression, regressionwindow-wanted})

Trunk
x86_64
Linux
regression, regressionwindow-wanted

Firefox Tracking Flags

(Not tracked)

Details

Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/18.0 Firefox/18.0 SeaMonkey/2.15a1 ID:20120924143413 c-c:c652d0ae41a7 m-c:483913c82d2d

When I update add-ons, either via "Install Add-on from File" or by clicking a link at AMO, the doorhanger icon appears at the left end of my URL bar but no doorhanger unfolds; and yet, the next click anywhere will have no effect, as if it were "closing" the invisible doorhanger. Similarly, repeatedly clicking that doorhanger icon makes a dotted line appear and disappear around it.

This has been going for some time (a couple of weeks, maybe); I'm not sure exactly when it appeared.
That's not provided by the Add-ons Manager, it's Seamonkey's UI.
Component: Add-ons Manager → General
Product: Toolkit → SeaMonkey

Comment 2

6 years ago
Door hanger problem => Neil is our expert on doorhangers.

Comment 3

6 years ago
Out of interest, if you set the doorhanger preference to false in about:config and restart and try those steps, what UI do you get instead?
(In reply to neil@parkwaycc.co.uk from comment #3)
> Out of interest, if you set the doorhanger preference to false in
> about:config and restart and try those steps, what UI do you get instead?

Hm, Filtering about:config for "doorh" I see two prefs:
browser.doorhanger.enabled            default     true
extensions.UpdateAddon.DoorHanger     default     false

The latter might be from the Add-on Update Checker extension which I installed a week or two ago. I'll play with both of these prefs and see what happens.

Comment 5

6 years ago
> browser.doorhanger.enabled
You need this one.
(In reply to Philip Chee from comment #5)
> > browser.doorhanger.enabled
> You need this one.

Yes, but I thought maybe that extension was misbehaving. No such luck: after disabling it, no change.
After setting browser.doorhanger.enabled to false and restarting, I get a notification bar. (Add-on Update Checker is still disabled.)

Comment 8

6 years ago
I tried the default theme on Linux and Windows, and also EarlyBlue on Windows (sorry I can't restart my Linux build right now) and I had no problems seeing the addonInstallComplete notification.

Sample error console snippet:
top.opener.getBrowser().getNotificationBox().addonInstallComplete({installs:[{name:"Lightning",addon:{pendingOperations:0}}]})
Checking the error console ought to be part of my muscle memory by now, but it isn't. I see this on add-on install (of Lightning & gdata-provider) with browser.doorhanger.enabled defaulted to true:

Warning: ReferenceError: reference to undefined property aInstall.icons[32]
Source file: resource://app/modules/XPIProvider.jsm
Line: 5223

When user ser to false, I get something very similar which I didn't write down. I just clicked "All" on the error console and that warning (which hasn't yet disappeared) appears to be immediately _followed_ by the following messages:

LOG addons.xpi: Starting install of file:///root/.download/mozilla/ext_sm/gdata-provider.xpi
 ----------
LOG addons.xpi: Addon {a62ef8ec-5fdc-40c2-873c-223b8a6925cc} will be installed as an unpacked directory
 ----------
LOG addons.xpi: Starting install of file:///root/.download/mozilla/ext_sm/lightning.xpi
 ----------
LOG addons.xpi: Addon {e2fda1a4-762b-4020-b5ad-a41df1933103} will be installed as an unpacked directory
 ----------
LOG addons.xpi: Install of file:///root/.download/mozilla/ext_sm/gdata-provider.xpi completed.
 ----------
LOG addons.xpi: Install of file:///root/.download/mozilla/ext_sm/lightning.xpi completed.
 ----------
Warning: WARN addons.manager: Exception calling callback: TypeError: document.getElementById(...).getString is not a function
Source file: chrome://optionsmenu/content/OptionsMenu.js
Line: 165
 ----------
Warning: WARN addons.manager: Exception calling callback: TypeError: document.getElementById(...).getString is not a function
Source file: chrome://optionsmenu/content/OptionsMenu.js
Line: 165
 ----------
Warning: WARN addons.manager: Exception calling callback: TypeError: document.getElementById(...).getString is not a function
Source file: chrome://optionsmenu/content/OptionsMenu.js
Line: 165
 ----------
Warning: WARN addons.manager: Exception calling callback: TypeError: document.getElementById(...).getString is not a function
Source file: chrome://optionsmenu/content/OptionsMenu.js
Line: 165
 ----------
LOG addons.updates: Requesting https://versioncheck.addons.mozilla.org/update/VersionCheck.php?reqVersion=2&id=skypilot@projectit.com&version=1.2.20080705&maxAppVersion=3.0.0.*&status=userDisabled&appID={92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}&appVersion=2.15a1&appOS=Linux&appABI=x86_64-gcc3&locale=en-US&currentAppVersion=2.15a1&updateType=97&compatMode=ignore

etc.



When I try to "Evaluate" your snippet in the error console (with Console² 0.9 installed and browser.doorhanger.enabled true), nothing happens. Not even a doorhanger icon (which does appear in the URL bar when I "really" install an add-on). Also no new error console message.

Comment 10

6 years ago
> Source file: chrome://optionsmenu/content/OptionsMenu.js
That rings a bell try updating to the latest Options Menu extension or disable it.
(In reply to Philip Chee from comment #10)
> > Source file: chrome://optionsmenu/content/OptionsMenu.js
> That rings a bell try updating to the latest Options Menu extension or
> disable it.

Extension Options Menu 2.5 is already the latest version available at AMO.

After disabling it, no change (no visible doorhanger but mouse clicks are eaten up as though there were one).
A wild idea: could this bug be related with bug 790918? Some images, especially maps on various sites but also some Facebook images, are displayed correctly in Firefox but not in SeaMonkey, where they seem to be completely transparent, letting the background shine through, except where smaller elements, such as the "You are here" pointer on maps, or tags on Facebook, are overlaid to them.

Hm, bug 790918 is in content but this is in chrome, yet both are about elements behaving as if 0% opaque. A wild idea, as I said. I'm throwing it on the wall to see if it sticks.
I notice the following line in about:config

  extensions.UpdateAddon.DoorHanger   default   boolean   false

Don't know if relevant.

Comment 14

5 years ago
>   extensions.UpdateAddon.DoorHanger   default   boolean   false
This pref does not exist on trunk.
(In reply to Philip Chee from comment #14)
> >   extensions.UpdateAddon.DoorHanger   default   boolean   false
> This pref does not exist on trunk.

Then I suppose it's a pref for some add-on I have, probably "Addon Update Checker".
You need to log in before you can comment on or make changes to this bug.