| commit | 32a0dea47c5b4cf1c05106577551882cdf85f85a | |
| author | Mugurell <Mugurell@users.noreply.github.com> | |
| Mon, 17 Jan 2022 17:24:36 +0000 (17 19:24 +0200) | ||
| committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | |
| Tue, 18 Jan 2022 08:37:04 +0000 (18 08:37 +0000) | ||
| tree | b9c952e685ab03c7b996bcd1be81cd20d036dd68 | treesnapshot (tar.gz zip) |
| parent | 84cc4f59cdb0614e5a1093ed4acec78d01d6f8db | commitdiff |
[components] For https://github.com/mozilla-mobile/android-components/issues/11527 - Allow the decor view time to process the incoming insets
There was a race between how insets are applied when entering immersive mode
and enabling immersive mode restore by setting an insets listener which is now
resolved by ensuring the decor view has the time needed to process the incoming
insets, solution recommended on issuetracker
https://issuetracker.google.com/u/2/issues/214012501 .
Removed the onWindowFocusChangeListener extension property since by having to
offer it through a getter the current implementation would always leak the old
one.
Fenix wasn't using it when this APIs allowed Fenix to pass such a listener and
there was no issue observed so there should be no observable negative impact.
There was a race between how insets are applied when entering immersive mode
and enabling immersive mode restore by setting an insets listener which is now
resolved by ensuring the decor view has the time needed to process the incoming
insets, solution recommended on issuetracker
https://issuetracker.google.com/u/2/issues/214012501 .
Removed the onWindowFocusChangeListener extension property since by having to
offer it through a getter the current implementation would always leak the old
one.
Fenix wasn't using it when this APIs allowed Fenix to pass such a listener and
there was no issue observed so there should be no observable negative impact.