Closed
Bug 832412
Opened 12 years ago
Closed 12 years ago
Location permissions screen overlays screen until an option is selected
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(b2g18+)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
b2g18 | + | --- |
People
(Reporter: tdowner, Assigned: vingtetun)
References
Details
(Keywords: b2g-testdriver, unagi, Whiteboard: u=fx-os-user c=may-6-17 p=1)
Attachments
(2 files, 1 obsolete file)
7.34 KB,
patch
|
etienne
:
review+
|
Details | Diff | Splinter Review |
585 bytes,
patch
|
etienne
:
review+
|
Details | Diff | Splinter Review |
Open up Camera app, Location permission screen appears. Press home button. Camera app go away, but location permission page won't until you select an option. The permission screen should go away with the home button press.
Updated•12 years ago
|
Whiteboard: DUPEME
Updated•12 years ago
|
Assignee: nobody → 21
Whiteboard: DUPEME → DUPEME, u=fx-os-user c=may-6-17 p=0
Updated•12 years ago
|
Whiteboard: DUPEME, u=fx-os-user c=may-6-17 p=0 → DUPEME, u=fx-os-user c=may-6-17 p=1
Updated•12 years ago
|
Whiteboard: DUPEME, u=fx-os-user c=may-6-17 p=1 → u=fx-os-user c=may-6-17 p=1
Assignee | ||
Comment 2•12 years ago
|
||
The bug is way less visible those days since the platform checks for the visibility of the app before sending a prompt message. Sadly the visibility of the app is changed at a good time for screenshot but a bad time for this when the user hit the home button. As a result the bug still happens if you open the camera app, wait for 1 second and a half and then hit the home button. Timing is important to reproduce it now.
I'm going to add a new API to monitor the visibility of the mozbrowser element in order to fire an event to cancel the request if needed. I don't see any other proper way.
Depends on: 868816
Assignee | ||
Comment 3•12 years ago
|
||
Assignee | ||
Comment 4•12 years ago
|
||
Etienne since you played with visibility the last time I'm asking you the review for both the Gecko and Gaia part.
Attachment #750980 -
Attachment is obsolete: true
Attachment #751114 -
Flags: review?(etienne)
Assignee | ||
Comment 5•12 years ago
|
||
Attachment #751115 -
Flags: review?(etienne)
Updated•12 years ago
|
Attachment #751115 -
Flags: review?(etienne) → review+
Comment 6•12 years ago
|
||
Comment on attachment 751114 [details] [diff] [review]
Gecko patch
Review of attachment 751114 [details] [diff] [review]:
-----------------------------------------------------------------
r=me with the nits addressed
::: b2g/components/ContentPermissionPrompt.js
@@ +161,5 @@
> + // away but the request is still here.
> + frame.addEventListener("mozbrowservisibilitychange", onVisibilityChange);
> +
> + self.delegatePrompt(request, requestId, function onCallback() {
> + frame.addEventListener("mozbrowservisibilitychange", onVisibilityChange);
adding it twice?
@@ +167,3 @@
> };
> +
> + // Something went wront. Let's cancel the request just in case.
s/wront/wrong
Attachment #751114 -
Flags: review?(etienne) → review+
Assignee | ||
Comment 7•12 years ago
|
||
Status: NEW → ASSIGNED
Assignee | ||
Comment 8•12 years ago
|
||
Comment 9•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Flags: in-moztrap?
Comment 10•11 years ago
|
||
Created a test case for checking when using the home button ends the prompt until going back into the app.
https://moztrap.mozilla.org/manage/cases/?filter-id=9253
Flags: in-moztrap?(dwatson) → in-moztrap+
You need to log in
before you can comment on or make changes to this bug.
Description
•