========
https://hg.mozilla.org/integration/gaia-central/rev/7a3779b3fbbc
Author: Ryan VanderMeulen <rvandermeulen@mozilla.com>
Desc: Revert "Merge pull request #31529 from rickychien/b2g-43"
This reverts commit 61385bf8a2063f256b546ea5dffb90a53c12876c, reversing
changes made to 7e36fb3976bc8aab4ef7cbb37e6c79145b3d4717.
========
https://hg.mozilla.org/integration/gaia-central/rev/0164a51c5b86
Author: Ryan VanderMeulen <ryanvm@gmail.com>
Desc: Merge pull request #31109 from cr/pctofix
Bug 1181571 - Fix lockscreen delay issue
========
https://hg.mozilla.org/integration/gaia-central/rev/87828a5b67d4
Author: Christiane Ruetten <cr@mozilla.com>
Desc: Fix TypeError: this.emergencyCallBtn is null
========
https://hg.mozilla.org/integration/gaia-central/rev/c07276bb5364
Author: Christiane Ruetten <cr@mozilla.com>
Desc: Overhaul tests for new internal InputPad logic
========
https://hg.mozilla.org/integration/gaia-central/rev/4ec9fe1337dc
Author: Christiane Ruetten <cr@mozilla.com>
Desc: Finalizing tests
Tests now working. Solved by creating a setTimeout stub that forces
synchronicity. Also removed onPasscodeValidationFailed trigger check
on wrong pass code, because I can't make the promise resolve before
the test ends without code changes in the test subject.
========
https://hg.mozilla.org/integration/gaia-central/rev/caf1b7db97bd
Author: Christiane Ruetten <cr@mozilla.com>
Desc: Add comment on event flow
========
https://hg.mozilla.org/integration/gaia-central/rev/230ebd40b450
Author: Christiane Ruetten <cr@mozilla.com>
Desc: Fix comment
========
https://hg.mozilla.org/integration/gaia-central/rev/4328ada81707
Author: Christiane Ruetten <cr@mozilla.com>
Desc: Add test prototypes for pass code handling
========
https://hg.mozilla.org/integration/gaia-central/rev/87581a852a13
Author: Christiane Ruetten <cr@mozilla.com>
Desc: Fixing lockscreen delay bypass by rewriting core logic
This is fixing bug 1181571 where lockscreen delay on repeated pass code
failure could be trivially bypassed by pressing the home button. The
faulty behavior was caused by a limitation of the previous architecture
which was only making the delay occurr *after* a wrong pass code had
been entered. Consequently, whenever the input pad would be restarted,
like after closing it with the home button or when a screen timeout
occurred, the pending delay would not persist and pass code entry would
be accepted right away.
The fix made it necessary to rewrite parts of lockscreen's messaging
and state handling. Previous changes in architecture caused pass code
failure counting and delay timer handling to be maintained in two
places: in LockScreen (for pass code checking) and in LockScreenInputPad
(for displaying error state to the user). Logic error even caused the
two states to get out of sync under certain conditions.
Now state and timeout related to pass code checking are maintained
exclusively by LockScreen, which signals LockScreenInputManager with
three distinct messages of failure (on wrong pass code), reset (after
error delay has passed), and success (on correct pass code).
LockScreenInputPad now is always aware of a passcode error delay ongoing
in LockScreen, every UI update is rendered according to this state, and
key input is ignored when necessary.
