Closed
Bug 938262
Opened 12 years ago
Closed 12 years ago
[B2G][Settings] Camera app permissions displays "Ask" even after a selection is made and Settings is reopened
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(blocking-b2g:hd+, b2g-v1.1hd fixed, b2g-v1.2 fixed)
VERIFIED
FIXED
| blocking-b2g | hd+ |
People
(Reporter: dwatson, Assigned: arthurcc)
References
Details
(Keywords: regression)
Attachments
(2 files)
Repro Steps:
1. Load Buri Build ID: 20131113004000
2. Open Settings app
3. Select "App Permissions"
4. Tap on Camera
5. Tap on the Drop-down
6. Select Grant or Deny
7. Close the app(Through the Card View)
8. Reopen Settings app and go back to the Camera App permissions
Actual Results:
The App Permission does not stay on the selection made.
Expected Results:
App Permissions will maintain the selection and will stay after closing the app and/ or a reboot.
Environmental Variables
Device: Buri v1.2 MOZ RIL
Build ID: 20131113004000
Gecko: http://hg.mozilla.org/releases/mozilla-b2g26_v1_2/rev/3fc449c858e6
Gaia: 20e8d407dac3bb2ad2616e8c2d8678d70fd82fa0
Platform Version: 26.0
Base Build: 20131104
Updated•12 years ago
|
blocking-b2g: --- → koi?
Keywords: regression,
regressionwindow-wanted
Comment 1•12 years ago
|
||
I can reproduce - seems like the UI is busted with maintaining selection entities in general.
Updated•12 years ago
|
QA Contact: sparsons
Comment 2•12 years ago
|
||
Issues starting occurring with the permission section of the settings on the Buri 1.2 Build ID: 20130905185329. In this build (9/05) through the 9/10 1.2 build, if the user selects an app to change the permissions, the screen turns white, and the user will have to kill the settings app in the task manager, and reopen. On the 9/11 build to the present 1.2 build, the issue in comment 0 reproduces as described.
-First Broken-
Gaia b77dc7d399c14ac2bafe5c89566b292bc6772d32
SourceStamp df8f342e9a6b
BuildID 20130905185329
Version 26.0a1
-Last working-
Gaia b6c5bf1d24230bfed4a8f680e625fa2175001f82
SourceStamp 7ff96bd19c1c
BuildID 20130904040205
Version 26.0a1
Keywords: regressionwindow-wanted
Comment 5•12 years ago
|
||
Arthur, is this part of our work? I don't think so.
The commits that touches apps/settings directory are:
Bug 901227, Bug 891743, Bug 908949, Bug 883565, Bug 910316
Kevin, would it possible if you patch triggered the regression?
Flags: needinfo?(timdream)
Flags: needinfo?(kgrandon)
Flags: needinfo?(arthur.chen)
| Assignee | ||
Comment 6•12 years ago
|
||
This was regressed by bug 907708. (https://github.com/mozilla-b2g/gaia/commit/a17731400321f7fe57be1d810493fb335f9eb471)
Flags: needinfo?(kgrandon)
Flags: needinfo?(arthur.chen)
| Assignee | ||
Updated•12 years ago
|
Assignee: nobody → arthur.chen
| Assignee | ||
Comment 7•12 years ago
|
||
Evelyn, could you help review the change? Thanks!
Attachment #832795 -
Flags: review?(ehung)
Comment 8•12 years ago
|
||
Ah, I am not good at regression range...
Comment 9•12 years ago
|
||
Comment on attachment 832795 [details]
link to https://github.com/mozilla-b2g/gaia/pull/13735
in bug 907708, I suggest using `select.options[select.selectedIndex].textContent` because I want the fake button displaying "text(meaning)" instead of "value". (see bug 907708 comment 7) But obviously I made mistake and caused the regression here.
However, I still think we should not display value on the fake button, can you also fix this too?
Attachment #832795 -
Flags: review?(ehung) → review+
Comment 10•12 years ago
|
||
Sounds like if bug 907708 caused this means this should be uplifted to 1.1 HD.
Blocks: 907708
blocking-b2g: koi+ → hd?
Comment 11•12 years ago
|
||
regressed by 907708, which has not been landed on HD as of now yet.
Arthur, can you check if bug 938626 will cause this regression as well? KGrandon suggests we fix 907708 by landing 938626 instead. Please NI or ping me once you confirm thanks ;)
Flags: needinfo?(arthur.chen)
Comment 12•12 years ago
|
||
Sorry I mean bug 929840 where I mentioned 938626 in my last comment.
| Assignee | ||
Comment 13•12 years ago
|
||
Comment on attachment 832795 [details]
link to https://github.com/mozilla-b2g/gaia/pull/13735
Evelyn, I updated the patch to address the comment. Could you review it again? Thanks.
Attachment #832795 -
Flags: review+ → review?(ehung)
Comment 14•12 years ago
|
||
(In reply to Wayne Chang [:wchang] from comment #11)
> regressed by 907708, which has not been landed on HD as of now yet.
>
> Arthur, can you check if bug 929840 will cause this regression as well?
> KGrandon suggests we fix 907708 by landing 938626 instead. Please NI or ping
> me once you confirm thanks ;)
No, I won't suggest uplift bug 929840 to fix the regression of bug 907708.
As KGrandon commentted on bug 907708 comment 32, there are a lot of conflicts. Arthur's patch in this bug is relatively simple, it's safer, I think.
Flags: needinfo?(arthur.chen) → needinfo?(wchang)
Comment 15•12 years ago
|
||
Thanks, lets take the patches here to address regressions from bug 907708 then.
I will remove HD+ from bug 929840.
blocking-b2g: hd? → hd+
Flags: needinfo?(wchang)
Comment 16•12 years ago
|
||
Comment on attachment 832795 [details]
link to https://github.com/mozilla-b2g/gaia/pull/13735
Thanks for fixing this regression!
Attachment #832795 -
Flags: review?(ehung) → review+
| Assignee | ||
Comment 17•12 years ago
|
||
master: 7f0b92dec4d87a7b618b628149b49a18dbd9dbc8
This issue was regressed by bug 907708, please don't uplift the patch to hd until bug 907708 gets uplifted.
Comment 18•12 years ago
|
||
(In reply to Arthur Chen [:arthurcc] from comment #17)
> master: 7f0b92dec4d87a7b618b628149b49a18dbd9dbc8
>
> This issue was regressed by bug 907708, please don't uplift the patch to hd
> until bug 907708 gets uplifted.
Well, we shouldn't uplift this to 1.1 HD yet, but we should uplift it to 1.2. 1.2 does have the regressing patch in the build.
Comment 19•12 years ago
|
||
v1.1.0hd: cc01ba1738d227dcf263ad5736cddd6925bddfbe
I was not being able to uplift to v1.2 due to conflicts.
Flags: needinfo?(arthur.chen)
| Assignee | ||
Comment 20•12 years ago
|
||
Comment 17 is wrong. The patch is for v1.2 and the bug has already been fixed on v1.2.
v1.2: 7f0b92dec4d87a7b618b628149b49a18dbd9dbc8
Flags: needinfo?(arthur.chen)
Comment 21•12 years ago
|
||
Looks fine on trunk - basic checks with the camera app w/app perms page worked as expected.
Status: RESOLVED → VERIFIED
Keywords: verifyme
You need to log in
before you can comment on or make changes to this bug.
Description
•