Closed Bug 674734 Opened 13 years ago Closed 12 years ago

Explicitly tab/app-modal popups

Categories

(Core :: General, defect)

Product:
Core
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME
Project Flags:
blocking-basecamp -

People

(Reporter: cjones, Unassigned)

References

Details

We recently made all content-thrown popups (alert/confirm) be tab-modal (equiv. app-modal) instead of window-modal (equiv. system-modal). That's great, but we'll need to restore system-modal popups for things like phone apps (bug 674726), where a notification of an incoming phone call really will need to interrupt whatever the user is doing in whatever tab/app. Whether we want to restore the old behavior for trusted apps (phone app), or add new explicitly-system-modal-popup API is an issue for another bug. In any case, we need explicitly-app-modal-popup API. Why? The phone app itself might want to throw an app-modal popup and shouldn't have to worry about whether it's accidentally throwing a system-modal popup.
OS: Linux → All
Hardware: x86_64 → All
No longer blocks: b2g-product-phone
Whiteboard: [b2g:blocking-]
blocking-basecamp: --- → -
Whiteboard: [b2g:blocking-]
Popups are app-modal by default, and the "attention screen" ~hack gets us the system-modal behavior.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.