Closed Bug 1078111 Opened 10 years ago Closed 6 years ago

LockscreenWindow should fire the requestclose event instead of request-unlock on LockscreenWindowManager

Categories

(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: alive, Unassigned)

References

Details

See bug 1076327 comment 17.

One of the issues is VisibilityManager using lockscreen-request-unlock to fire the showwindow event
* There is a race (fixed in bug 1076327 but we don't know if there is still some)
* Inconsistent pattern with other event

One way worthy to try is make LockscreenWindow to fire requestclose event with notification/activity infomation.

The event route looks like:

Lockscreen app =(request-unlock event from IAC or System.request, will be transfered to mozbrowserclose later)=> LockscreenWindow =(requestclose)=> LockscreenWindowManager =(close)=> LockscreenWindow =(closing)=> VisibilityManager =(showwindow)=> AppWindowManager


Greg please put this one in your queue.
Flags: needinfo?(gweng)
Summary: Home screen does not appear → LockscreenWindow should fire the requestclose event instead of request-unlock on LockscreenWindowManager
Assignee: nobody → gweng
Flags: needinfo?(gweng)
Severity: blocker → normal
Priority: P1 → --
Assignee: gweng → nobody
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.