Closed
Bug 716704
Opened 13 years ago
Closed 12 years ago
Ensure alert/prompt/etc are tab-modal by default
Categories
(Firefox OS Graveyard :: General, defect)
Firefox OS Graveyard
General
Tracking
(blocking-kilimanjaro:+, blocking-basecamp:+)
RESOLVED
FIXED
People
(Reporter: cjones, Unassigned)
References
Details
(Whiteboard: [qa+])
I thought they were tab-modal by default, but I hear now it's up to the browser binding and implementation of nsIPromptService.
Reporter | ||
Comment 1•13 years ago
|
||
More precisely, these should be modal to the "outer" iframe that throws them, in the window.top sense. So dialogs shouldn't escape <iframe app>, nor should they escape <iframe browser>. But an alert from an inner iframe in an <iframe browser> should bubble out.
Updated•13 years ago
|
OS: Linux → All
Hardware: x86_64 → All
Updated•12 years ago
|
Blocks: b2g-product-phone
Updated•12 years ago
|
No longer blocks: b2g-demo-phone
Updated•12 years ago
|
blocking-basecamp: --- → +
blocking-kilimanjaro: --- → +
Whiteboard: [b2g:blocking+]
Reporter | ||
Comment 3•12 years ago
|
||
This was fixed by jlebar's mozbrowser work.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 4•12 years ago
|
||
QA: please find an owner to verify this bug and/or set of dependencies.
Whiteboard: [qa+]
Comment 5•12 years ago
|
||
(In reply to Stephen Donner [:stephend] from comment #4)
> QA: please find an owner to verify this bug and/or set of dependencies.
This sounds like this affects the browser app, right?
You need to log in
before you can comment on or make changes to this bug.
Description
•