942013 - Memchaser cannot be removed from UI in Australis

Status: RESOLVED FIXED

(Add-on SDK Graveyard :: General, defect)

Description

[Fanolian]

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

Steps to reproduce:

Please test it in a new profile as it may ruin the UI permanently

1. In a new profile, install memchaser 0.5.2.1 at https://addons.mozilla.org/En-us/firefox/addon/memchaser/versions/ .
2. Go to the customize toolbar page. Try to drag memchaser to another toolbar, e.g. tab bar or menu bar.
3. Without leaving the customization page, try dragging memchaser to another location. It should work for now.
4. Restart Nightly. Go to customize and try to drag memchaser to another toolbar.


Actual results:

Memchaser can be reordered within the same toolbar only. It cannot be removed or moved to another toolbar.
Pressing "Restore Defaults" from the customization page does not work for memchaser neither.


Expected results:

I can (re)move memchaser from UI at ease.

This bug was originally filed at https://github.com/mozilla/memchaser/issues/182 but whimboo thinks it is Add-on SDK related.

Comment 1

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

Related to bug 912656, perhaps?

Comment 2

[:Gijs (he/him)]

This is the unfortunate consequence of the Add-on SDK fixes for both bug 854226 and bug 931092 still not having been uplifted. I'm not sure if it's useful to keep this bug around, I'll leave that up to you.

Comment 3

[:Gijs (he/him)]

(In reply to :Gijs Kruitbosch from comment #2)
> This is the unfortunate consequence of the Add-on SDK fixes for both bug
> 854226 and bug 931092 still not having been uplifted. I'm not sure if it's
> useful to keep this bug around, I'll leave that up to you.

These are in Nightly as of today. After having updated to that Nightly, can someone confirm this is fixed now?

Comment 4

[Fanolian]

(In reply to :Gijs Kruitbosch from comment #3)
> (In reply to :Gijs Kruitbosch from comment #2)
> > This is the unfortunate consequence of the Add-on SDK fixes for both bug
> > 854226 and bug 931092 still not having been uplifted. I'm not sure if it's
> > useful to keep this bug around, I'll leave that up to you.
> 
> These are in Nightly as of today. After having updated to that Nightly, can
> someone confirm this is fixed now?

I can confirm that it is fixed as of today's Nightly (2013-11-29).

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Great to hear that. Thank you for testing, Fanolian! Marking this bug as fixed based on comment 4.