Closed Bug 1047348 Opened 9 years ago Closed 6 years ago

Incorrect positioning of SocialAPI location sharing doorhanger after changing position of icon and restart


(Firefox Graveyard :: SocialAPI, defect)

Windows 7
Not set


(firefox31 wontfix, firefox32- wontfix, firefox33- wontfix, firefox34 affected)

Tracking Status
firefox31 --- wontfix
firefox32 - wontfix
firefox33 - wontfix
firefox34 --- affected


(Reporter: FlorinMezei, Unassigned)


Reproducible with:
Firefox 32 Beta 3 - 20140731191115 - User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0
Latest Firefox 33 Aurora - 20140731004002
Latest Firefox 34 Nightly - 20140731030206

Environment: Windows 7 x64, Windows XP x86, Windows 8 x64

Steps to reproduce:
1. Open Firefox with new profile.
2. Go to and choose to activate the Demo Social Service.
3. Choose to enable the service ---> SocialAPI panel displays on the right, with location sharing doorhanger displayed under the title bar = OK
4. Choose "Share location", then open the Customization Panel, choose "Customize" and move the Social Demo icon to the right of the Tab strip.
5. Restart Firefox and see where the SocialAPI location sharing doorhanger displays. Repeat this step a few times.

Expected results: 
The doorhanger always displays in the SocialAPI Demo panel, under the title bar, same as at step #3.

Actual results:
Sometimes the doorhanger displays under one of the open tabs. 

- see "" 
- I was able to reproduce this in Firefox 29.0.1 as well, so it's no recent regression
Version: 32 Branch → Trunk
[Tracking Requested - why for this release]:
The geolocation in the demo provider is to test the permissions panel will appear, however no current providers use anything that produces a permissions prompt from the sideabar. I don't see a reason to chase this down right now (especially for uplifting).
Flags: firefox-backlog? → firefox-backlog+
deprecation in fx51
Closed: 6 years ago
Resolution: --- → WONTFIX
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.