Closed
Bug 1174910
Opened 9 years ago
Closed 6 years ago
[Aries][Theme Editor] There is no option to set the theme in the studio app
Categories
(Firefox OS Graveyard :: Gaia::Theme Editor, defect)
Tracking
(blocking-b2g:-, b2g-master affected)
People
(Reporter: AdamA, Assigned: hub)
References
Details
(Whiteboard: [3.0-Daily-Testing][Spark])
Attachments
(2 files)
Description: In the studio app there is no option to set the theme within the app. If you choose to enable a theme it will set that theme as yours and add it to the list of options in settings, but you cannot enable a theme more than once so you will have to go into settings to switch themes for testing. Repro Steps: 1) Update a Aries to 20150614233012 2) Open the studio app 3) Make a new theme 4) Choose to Enable the theme 5) Repeat steps 3-4 6) Go back to the first theme in studio 7) Observe enable button grayed out Actual: User has to go to settings to change themes Expected: It is expected that users are able to change themes in the studio app Environmental Variables: Device: Aries 3.0 (Full Flash) Build ID: 20150614233012 Gaia: 0e151b76cbe66ae5792625e6feae9cf5741b3467 Gecko: 3c26bef95d54 Gonk: 75c7e6ca80d0c7a53f346ecfcde2343be95808c9 Version: 41.0a1 (3.0) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0 Repro frequency: 10/10 See attached: screenshot, logcat
Reporter | ||
Comment 1•9 years ago
|
||
Reporter | ||
Updated•9 years ago
|
Blocks: Foxfood-papercuts
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-master:
--- → affected
Flags: needinfo?(pbylenga)
Whiteboard: [3.0-Daily-Testing][Spark]
Comment 2•9 years ago
|
||
[Blocking Requested - why for this release]: Functional issue of a main UX flow.
blocking-b2g: --- → spark?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
Flags: needinfo?(firefoxos-ux-bugzilla)
This doesn't look like it's in the spec : https://mozilla.app.box.com/s/2rfhpr44jj4hoaulpsmu5tn6z31t7wsf
Comment 5•9 years ago
|
||
Marking bug 1177748 since it seems to be roughly the same. I think the basic problem is that, as a user, I don't know what the Studio app is doing. Having used Firefox OS as my only phone for over a 6 months I didn't even know themes existed so I had no idea that Studio was interacting with some themes feature. I thought Studio *was* the themes feature. I also have no idea why I can only apply a theme with Studio once. What am I actually applying? A theme? A theme customization? It's just odd that I have a one-time Enable button and no way to disable whatever I did. Also, the coloring of the Enable button does not make it obvious when it has been disabled.
Comment 6•9 years ago
|
||
Brian, it really sucks that this is a problem for you. While we work on a solution, here's a workaround for now: 1. Connect WebIDE to the System app. Copy and paste the script below [1] to the Scratchpad, modify it so that `theme` is the name of the theme that you want to use, and run it. NOTE: Yes, as part of this step, you're deleting the theme that you want to use. Bear with me. 2. Open Studio, tap on the theme that you want to use, and then hit "Duplicate". Enter the same name as it already had. 3. You'll now see two instances of that theme in the main menu. Delete the first one. 4. Go back to the second one and enable it. [1] ```js // Change this to the name of the theme that you want to delete. var theme = 'Solarized Light'; navigator.mozApps.mgmt.getAll().then(function(apps) { apps.forEach(function(app) { if (app.manifest.name === theme) { navigator.mozApps.mgmt.uninstall(app).onsuccess = function() { console.log('Successfully uninstalled ' + theme); }; } }); }); ```
blocking-b2g: spark? → 2.5?
Assignee | ||
Comment 8•9 years ago
|
||
I believe this is missing.
Assignee: nobody → hub
Status: NEW → ASSIGNED
Flags: needinfo?(hub)
Comment 9•9 years ago
|
||
passing to J for comment. Thanks and sorry for the delay!
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(jsavory)
Comment 10•9 years ago
|
||
The expected result is correct here, only the currently active theme should have a disabled 'enable' button. If the user enables a second theme, the first theme becomes available and the enable button should be tappable.
Flags: needinfo?(jsavory)
Comment 11•9 years ago
|
||
Studio will not ship on by default in 2.5, so minusing the blocking flag.
blocking-b2g: 2.5? → -
Comment 12•6 years ago
|
||
Firefox OS is not being worked on
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•