Closed Bug 1091306 Opened 10 years ago Closed 4 years ago

Eliminate page flicker when exiting editing mode on new tablet

Categories

(Firefox for Android Graveyard :: General, defect)

All
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: mcomella, Unassigned)

References

Details

0) With new tablet enabled
1) Go to a website (I used kotaku.com)
2) Click the url bar to enter editing mode
3) Click the menu button
4) Click "Request desktop site"

Expected: The page reappears and about:home disappears
Actual: The page reappears but flickers

Only possible after bug 1086981.
May not only be a new tablet issue - it looks like the keyboard reduces the size of the web content area and the flicker is seeing this reduced size and seeing the web content expand again.

Some solutions:
  1) Don't resize the web content area (but we have to resize it in other cases!)
  2) Wait until the keyboard is hidden before showing the web content area again (but we have no hooks!)

Maybe there's a better way.
Summary: Eliminate page flicker when exiting editing mode on the same page new tablet → Eliminate page flicker when exiting editing mode on new tablet
We're not doing anything about this in v1.
Blocks: new-tablet-v2
No longer blocks: new-tablet-v1
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.