Closed
Bug 1271481
Opened 9 years ago
Closed 7 years ago
Add interface to lightweight themes
Categories
(WebExtensions :: Frontend, defect, P5)
WebExtensions
Frontend
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: andy+bugzilla, Unassigned)
References
Details
(Whiteboard: [design-decision-approved][triaged])
Maybe we should add an interface lightweight themes so they could be controlled by an add-on:
https://developer.mozilla.org/en-US/Add-ons/Themes/Lightweight_themes
Since you can also do a lot of this from a HTML page as documented in bug 511771, and see example here https://bug511771.bmoattachments.org/attachment.cgi?id=457621.
I'm guessing the main advantage is the install would proceed without forcing a user prompt.
Also this might allow personas-plus and related add-ons to be moved to webextensions.
Updated•9 years ago
|
Whiteboard: [design-decision-needed] → [design-decision-needed] themes
Updated•9 years ago
|
Whiteboard: [design-decision-needed] themes → [design-decision-needed] themes triaged
Comment 1•9 years ago
|
||
I think we'd almost need a "themes" permission so that an add-on could access a theme specific API.
Reporter | ||
Comment 2•8 years ago
|
||
Spoke about this in London and was generally approved by the team.
The themes permission sounds good, do you think that should prompt a user about requiring that permission? Changing a theme is annoying, but doesn't impart any possible security or privacy concerns imho.
Whiteboard: [design-decision-needed] themes triaged → [design-decision-approved] themes triaged
Comment 3•8 years ago
|
||
> The themes permission sounds good, do you think that should prompt a user about requiring that permission? Changing a theme is annoying, but doesn't impart any possible security or privacy concerns imho.
I think the only thing that ever came up was if someone unwittingly changed to an inappropriate theme.
But I don't think that's enough to make this be a promptable permission.
Reporter | ||
Comment 4•8 years ago
|
||
Does this still make sense with your themes work Jared?
Blocks: webext-themes
Flags: needinfo?(jaws)
Reporter | ||
Updated•8 years ago
|
Component: WebExtensions: Untriaged → WebExtensions: Frontend
Priority: -- → P5
Comment 5•8 years ago
|
||
It's too early to tell yet. We're indeed experimenting with a WebExtension-based frontend for browser themes, but the 'real' work will be planned for Q1 2017. This plan will be highly influenced by feedback we receive on the result of our experiments and more generally from other parts of the community.
In other words: it's too early to tell.
Flags: needinfo?(jaws)
Comment 6•8 years ago
|
||
removed P5 and triaged for re-consideration before 57. Spoke with Andy about what is blocking Personas Plus. sounds like needing an API that allows installing a new theme from AMO is what's missing (based on Andreas' initial prototype).
Andreas, does this describe what you mentioned in ACE meeting today about needing in WE to migrate Personas Plus?
Flags: needinfo?(awagner)
Priority: P5 → --
Whiteboard: [design-decision-approved] themes triaged → [design-decision-approved]
Comment 7•8 years ago
|
||
There's also a question here about whether we add a new webextension API or expose one of our existing APIs (eg InstallTrigger or mozAddonManager). As unpleasant as adding yet another API sounds, the existing ones are pretty highly tailored to the specific ways they are used right now and expanding them to be usable from webextensions would be messy.
Reporter | ||
Comment 8•8 years ago
|
||
I propose we add a management.install(...) command that only allows you to do a theme. As matching what mixedpuppy has already done for setEnabled.
Comment 9•8 years ago
|
||
Yes, if we want to keep the functionality of Personas Plus, we'd need a way for it to install themes from AMO, preferably without the doorhanger, like we do on disco pane.
Flags: needinfo?(awagner)
Reporter | ||
Updated•7 years ago
|
Priority: -- → P5
Whiteboard: [design-decision-approved] → [design-decision-approved][triaged]
Reporter | ||
Comment 10•7 years ago
|
||
I believe we've got enough functionality now to allow Personas Plus to migrate, so closing this. Please let me know Andreas if that' not the case.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•