1225043 - "Undo" not works for enabling to default theme

Status: RESOLVED DUPLICATE of bug 1202654

(Toolkit :: Add-ons Manager, defect)

Description

[YF (Yang)]

Attachment: screenshot

STR:
Enabled a complete theme, disabling it to get Restart notification, click the Undo for enabling to default theme, no works.


Error: Cannot disable the default theme XPIProvider.jsm:6662:1 in Browser Console.


WONTFIX for this bug after bug 1222546 landed.

Comment 1

[Tony Mechelynck [:tonymec]]

UA:"Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 SeaMonkey/2.42a1" ID:20151111003002 c-c:1d7535f9bc102939d4c43523e9bb6f870fcfe1d5 m-c:cc473fe5dc512c450634506f68cbacfb40a06a23 en-US

I can reproduce the problem on the equivalent version of SeaMonkey for Linux64:

After clicking "Enable" for the default theme, the add-ons manager appears as in attachment 8687839 [details]. At that point, clicking "Undo" on the default theme indeed does nothing.

However, clicking "Enable" on the theme currently queued for disabling removes both themes from the enable/disable queue, restoring the former status with one exception: if a lightweight theme was set on top of the non-default complete theme, this lightweight theme is immediately disabled; to reenable it (on trunk) its ID must be set as the value of the string pref lightweightThemes.selectedThemeID in about:config, then the mouse hovered over any lightweight theme thumbnail at AMO, or in the "Lightweight Theme Manager" extension's page (opened at chrome://lwthemes/content/lwthemes.xul by the "Open" button in its Preferences) if installed.

I think that this "Undo" widget worked at some point in the past, but I can't be sure, and for the love of me I couldn't say when, if ever, it stopped working, so I don't set "regression" at the moment. More info is of course welcome.

Comment 2

[Tony Mechelynck [:tonymec]]

P.S. The test in comment #1 was done without opening the Error Console, which when opened afterwards scrolls so fast that finding a relevant message in it is hopeless on my installation anyway. I run SeaMonkey with its stdout/stderr logged to disk, but nothing relevant was found there either.