Zoom isn't restored after exiting fullscreen

RESOLVED FIXED in Firefox 65

Status

()

defect
P2
normal
RESOLVED FIXED
6 months ago
5 months ago

People

(Reporter: csheany, Assigned: botond)

Tracking

(Blocks 1 bug, {regression})

65 Branch
mozilla65
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox-esr60 unaffected, firefox63 unaffected, firefox64 wontfix, firefox65 fixed)

Details

Attachments

(1 attachment)

Reporter

Description

6 months ago
User Agent: Mozilla/5.0 (Android 7.1.1; Tablet; rv:65.0) Gecko/65.0 Firefox/65.0

Steps to reproduce:

1. Open https://www.mozilla.org/en-US/firefox/
2. Zoom in
3. Enter fullscreen of a video
4. Exit


Actual results:

The page is zoomed out


Expected results:

The page should still be zoomed in
Assignee

Comment 1

6 months ago
I can reproduce this intermittently. It looks like there may be a race condition between the code to restore the original zoom level that was added in bug 1493976, and some other code that is setting the zoom level.
Assignee

Comment 2

6 months ago
(In reply to Botond Ballo [:botond] from comment #1)
> and some other code that is setting the zoom level

Specifically, APZCCallbackHelper::UpdateRootFrame() [1].

[1] https://searchfox.org/mozilla-central/rev/8f0db72fb6e35414fb9a6fc88af19c69f332425f/gfx/layers/apz/util/APZCCallbackHelper.cpp#318
Component: General → Panning and Zooming
Product: Firefox for Android → Core
Version: Firefox 65 → 65 Branch
Assignee

Comment 3

6 months ago
We take this branch in NotifyLayersUpdated() [1] which has a comment that says:

  // Any change to the pres shell resolution was requested by APZ and is
  // already included in our zoom;

This is no longer true in light of bug 1493976.

[1] https://searchfox.org/mozilla-central/rev/8f0db72fb6e35414fb9a6fc88af19c69f332425f/gfx/layers/apz/src/AsyncPanZoomController.cpp#4323
Assignee

Updated

6 months ago
Assignee: nobody → botond
Assignee

Updated

6 months ago
Priority: -- → P2
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Assignee

Comment 4

6 months ago
The tracking is done using nsAtom origins, similarly to how updates to the
scroll offset are tracked.

Currently, APZ still uses some heuristics to deduce that the main thread
originated a resolution change in some cases, but the intention is to try
to remove those and rely only on this mechanism in the furture.

Comment 5

6 months ago
Pushed by bballo@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/79e8494d5df5
Track more accurately when the main thread originates a resolution change. r=kats
Assignee

Updated

6 months ago
Blocks: 1512273

Comment 6

6 months ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/79e8494d5df5
Status: ASSIGNED → RESOLVED
Last Resolved: 6 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
Assignee

Comment 7

5 months ago
Too late to uplift this on 64.
You need to log in before you can comment on or make changes to this bug.