[Australis] Bufferapp's extra addon button occupying the wrong spot on the toolbar

RESOLVED INVALID

Status

()

Firefox
Toolbars and Customization
RESOLVED INVALID
4 years ago
4 years ago

People

(Reporter: aks, Unassigned)

Tracking

(Blocks: 2 bugs)

28 Branch
x86_64
Windows 7
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Created attachment 8334369 [details]
bufferapp_toolbar.png

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0 (Beta/Release)
Build ID: 20131118094134

Steps to reproduce:

1. Open firefox nightly 28.0a1.
2. Install the bufferapp firefox addon from bufferapp.com/extras‎.
 


Actual results:

The toolbar has 2 bufferapp buttons, one of which is also at the wrong spot.


Expected results:

There should be only one addon button and at the right place.
Thanks for the report.

I guess we'll need to figure out what they're doing to see if it needs to be fixed on our side or theirs.
Blocks: 872617, 939862
Component: Untriaged → Toolbars and Customization

Updated

4 years ago
Summary: [Australis] Extra addon button occupying the wrong spot on the toolbar. → [Australis] Bufferapp's extra addon button occupying the wrong spot on the toolbar

Comment 2

4 years ago
(In reply to Matthew N. [:MattN] (catching up on reviews) from comment #1)
> Thanks for the report.
> 
> I guess we'll need to figure out what they're doing to see if it needs to be
> fixed on our side or theirs.

I've seen this before in other add-ons when investigating the top 100 add-ons. It's an add-on problem where they insertItem something in either the nav-bar or the addon-bar (which means it ends up in the customize target of the navbar) and then check if it's where they expect, and if not they appendChild it to the nav-bar again, IIRC. It needs to be fixed within the add-on. We definitely don't duplicate buttons. I'm going to mark this as INVALID.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.