Closed
Bug 1168516
Opened 10 years ago
Closed 10 years ago
Enable developer menu by default in Spark customization
Categories
(Firefox OS Graveyard :: Gaia::Build, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
2.2 S13 (29may)
People
(Reporter: drs, Assigned: daleharvey)
References
Details
(Whiteboard: [spark][systemsfe])
Attachments
(1 file)
See bug 1163889 comment 7.
The developer menu might be enabled by default if we ship with userdebug, but we can just enable within the Spark customization to be safe. We don't yet know what build we're going to be shipping with specifically, so we could also wait until we know and RESOLVE INVALID this if necessary.
Reporter | ||
Comment 1•10 years ago
|
||
Dale, what do you think? I'm leaning towards just setting this anyways and backing it out later if we don't need it. If you want to go ahead with this, could you take it?
Flags: needinfo?(dale)
Reporter | ||
Updated•10 years ago
|
Blocks: spark-dev-mode
Comment 3•10 years ago
|
||
Assignee | ||
Comment 4•10 years ago
|
||
Comment on attachment 8611284 [details]
[gaia] daleharvey:1168516 > mozilla-b2g:master
So I actually dont think we should depend on user vs userdebug vs eng build for these type of settings. We have done in the past and its always fustrating to be asking 'are you using an engineering build etc'
I think they should be explicitly enabled, hence the developer menu enabled by default too (its also usually disabled by default)
Attachment #8611284 -
Flags: review?(drs)
Reporter | ||
Comment 5•10 years ago
|
||
Comment on attachment 8611284 [details]
[gaia] daleharvey:1168516 > mozilla-b2g:master
(In reply to Dale Harvey (:daleharvey) from comment #4)
> Comment on attachment 8611284 [details]
> [gaia] daleharvey:1168516 > mozilla-b2g:master
>
> So I actually dont think we should depend on user vs userdebug vs eng build
> for these type of settings. We have done in the past and its always
> fustrating to be asking 'are you using an engineering build etc'
>
> I think they should be explicitly enabled, hence the developer menu enabled
> by default too (its also usually disabled by default)
Yeah, I agree, and that makes sense.
I'm r-'ing only because we can't enable developer mode by default due to security concerns. Please remove that line and enable only the "developer.menu.enabled" setting. If you'd like more background info, see bug 1160235 comment 8.
Attachment #8611284 -
Flags: review?(drs) → review-
Assignee | ||
Updated•10 years ago
|
Attachment #8611284 -
Flags: review- → review?(drs)
Reporter | ||
Updated•10 years ago
|
Attachment #8611284 -
Flags: review?(drs) → review+
Updated•10 years ago
|
Whiteboard: [spark] → [spark][systemsfe]
Target Milestone: --- → 2.2 S13 (29may)
Assignee | ||
Comment 6•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•