Closed
Bug 1075412
Opened 10 years ago
Closed 10 years ago
[woodduck][settings] Without SD card inserted, default write storage should not be able to chose SD card
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(blocking-b2g:-, b2g-v2.0 affected, b2g-v2.0M affected, b2g-v2.1 unaffected)
RESOLVED
WONTFIX
blocking-b2g | - |
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | affected |
b2g-v2.0M | --- | affected |
b2g-v2.1 | --- | unaffected |
People
(Reporter: jocheng, Unassigned)
References
Details
+++ This bug was initially created as a clone of Bug #1073391 +++
ALPS01749363
[Steps]
1.Power on the device without the SD card.
2.Launch Settings.
3.Tap Media Storage.
4.Tap Default media location.
5.Tap SD card.
[Expected result]
You can not change the default write storage as SD card when you power on the device without the SD card.
[Error]
You can also change the default write storage as SD card without the SD card.
[Notes]
See log.zip
Reporter | ||
Updated•10 years ago
|
blocking-b2g: --- → 2.0M?
Reporter | ||
Updated•10 years ago
|
Summary: [woodduck][settings] You can also change the default write storage as SD card without the SD card → [woodduck][settings] Without SD card inserted, default write storage should not be able to chose SD card
Reporter | ||
Updated•10 years ago
|
Comment 2•10 years ago
|
||
[Blocking Requested - why for this release]:
Since this is the generic bug, so we are asking if we want to uplift patch in 2.1 to 2.0, not 2.0m, I think.
Luke, could you help find out which patch/bug we want to uplift here? Thanks.
blocking-b2g: 2.0M? → 2.0?
Flags: needinfo?(lchang)
Reporter | ||
Updated•10 years ago
|
blocking-b2g: 2.0? → 2.0+
Comment 3•10 years ago
|
||
Hi Josh, this is the design for v2.0 and before. We have new design for v2.1 meta bug 922927, but it's not feasible to pick those patches from v2.1 to v2.0 because it's a huge change. Please help to communicate this, thank you!
blocking-b2g: 2.0+ → 2.0?
Flags: needinfo?(jocheng)
Reporter | ||
Comment 4•10 years ago
|
||
Per comment from Howie at comment 3. Change back to 2.0M+ for next Triage 10/8
Reporter | ||
Comment 5•10 years ago
|
||
Dear Luke,
per comment 3 from Howie. The behavior is changed in 2.1. Do you think we can fix this in 2.0 and 2.0M? Thanks!
status-b2g-v1.4:
affected → ---
Comment 6•10 years ago
|
||
The patch we need to uplift from Gaia part is bug 943825. As Howie mentioned, it's a huge change indeed and will lead high risk. Besides, bug 943825 depends on a Gecko patch of bug 1029403 which is only landed on v2.1 branch for now. To uplift this Gecko patch will also introduce some risk.
Since current behavior is by design on v2.0 and before (per comment 3), we may need to reconsider this bug as a feature request. According to that, change it back to 2.0m? first for next triage.
blocking-b2g: 2.0M+ → 2.0M?
Flags: needinfo?(lchang)
Reporter | ||
Comment 7•10 years ago
|
||
Triage:
For FF OS 2.0 this is by design.
Status: NEW → RESOLVED
blocking-b2g: 2.0M? → -
Closed: 10 years ago
Resolution: --- → WONTFIX
Reporter | ||
Updated•10 years ago
|
Blocks: Woodduck_Blocker
Reporter | ||
Updated•10 years ago
|
Whiteboard: [partner-blocker]
Reporter | ||
Updated•10 years ago
|
Blocks: Woodduck_P2
Reporter | ||
Updated•10 years ago
|
No longer blocks: Woodduck_P2
You need to log in
before you can comment on or make changes to this bug.
Description
•