If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Show that a WebExtension has called theme.update

NEW
Unassigned

Status

()

Toolkit
WebExtensions: Frontend
P3
normal
3 months ago
2 months ago

People

(Reporter: andym, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [triaged])

(Reporter)

Description

3 months ago
You can enable a theme by going to about:addons, or the customise menu. However a  WebExtension can then call theme.update() and change the appearance. Returning to about:addons or the customise menu gives the user no idea that the theme has changed.

Perhaps we should show something about that.
(Reporter)

Updated

3 months ago
Priority: -- → P3
Whiteboard: [triaged]
(In reply to Andy McKay [:andym] from comment #0)
> You can enable a theme by going to about:addons, or the customise menu.
> However a  WebExtension can then call theme.update() and change the
> appearance. Returning to about:addons or the customise menu gives the user
> no idea that the theme has changed.
> 
> Perhaps we should show something about that.

Why can extensions do that? And why is that change not reflected in the UI?
You need to log in before you can comment on or make changes to this bug.