Closed
Bug 946139
Opened 11 years ago
Closed 11 years ago
[LockScreen] Make lockscreen unlocking strategy customizable
Categories
(Firefox OS Graveyard :: Gaia::System::Lockscreen, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gweng, Assigned: gweng)
References
Details
Attachments
(1 file)
To avoid a fixed strategy that can't be reused.
This is blocking Bug 945096.
After this got landed, the incoming lockscreen can be integrated.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → gweng
Assignee | ||
Comment 1•11 years ago
|
||
Customizable, new options, modify some minor bugs.
Attachment #8342257 -
Flags: review?(timdream)
Updated•11 years ago
|
Attachment #8342257 -
Flags: review?(timdream) → review+
Assignee | ||
Comment 2•11 years ago
|
||
Travis was green: https://travis-ci.org/mozilla-b2g/gaia/builds/14964907
Assignee | ||
Comment 3•11 years ago
|
||
Assignee | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 4•11 years ago
|
||
This breaks screen reader support. You got rid of the click listener.
Assignee | ||
Comment 5•11 years ago
|
||
I'll fix it on Bug 943237 ASAP. The thing I am wondering is the previous implementation obviously didn't check if the `event.mozInputSource` as mentioned in the Bug 943237, but they can still work both when ScreenReader is on and off.
You need to log in
before you can comment on or make changes to this bug.
Description
•