Closed
Bug 984962
Opened 10 years ago
Closed 10 years ago
Need for an easy app update url and channel switching from Developper menu in settings
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gerard-majax, Assigned: janx)
References
Details
Attachments
(1 file)
To ease some work, being able to switch those URLs more easily would be awesome. Something like an Advanced Developper menu in Settings, hidden behind a pref or a magic trick would do the job.
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(anygregor)
Comment 1•10 years ago
|
||
Dogfood users might have to go there and change the channel. We should get some nice UX for this.
Flags: needinfo?(anygregor) → needinfo?(firefoxos-ux-bugzilla)
Comment 2•10 years ago
|
||
Flagging Omega for input on Settings.
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(ofeng)
Comment 3•10 years ago
|
||
Not quite understand the request, so here are some questions: 1. Are we putting something in "Settings > Developer"? 2. How many fields do we need? 3. Are these fields single line text input? Or a value selector with some predefined options?
Flags: needinfo?(ofeng)
Reporter | ||
Comment 4•10 years ago
|
||
(In reply to Omega Feng [:Omega] from comment #3) > Not quite understand the request, so here are some questions: > > 1. Are we putting something in "Settings > Developer"? That would be the idea. > 2. How many fields do we need? For now, I only see modification of app.update.channel and app.update.url. > 3. Are these fields single line text input? Or a value selector with some > predefined options? I would prefer single input.
Flags: needinfo?(ofeng)
Assignee | ||
Comment 7•10 years ago
|
||
Works but needs tests.
Assignee | ||
Comment 8•10 years ago
|
||
Comment on attachment 8405399 [details] [review] github pull request Actually I'm not sure if/how to test this. Do unit tests make sense here? How can I also cover the gecko part of this feature in bug #995206?
Attachment #8405399 -
Flags: review?(21)
Comment 9•10 years ago
|
||
Comment on attachment 8405399 [details] [review] github pull request Comment on github.
Attachment #8405399 -
Flags: review?(21)
Assignee | ||
Comment 10•10 years ago
|
||
Comment on attachment 8405399 [details] [review] github pull request Second try, please have a look. (Also, please feel free to r- my patches when you want them changed prior to landing. I don't mind, and bugzilla doesn't count resetting the `review` flag as an actual review.)
Attachment #8405399 -
Flags: review?(21)
Comment 11•10 years ago
|
||
Comment on attachment 8405399 [details] [review] github pull request Just make sure that the new pref name does not break updates, but since this pref is read-only it should be fine.
Attachment #8405399 -
Flags: review?(21) → review+
Comment 12•10 years ago
|
||
See bug 995124 for the updated UX spec.
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → janx
Assignee | ||
Updated•9 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•