Closed Bug 1690302 Opened 3 years ago Closed 2 years ago

[Bug] Background images are not fully rendered when the toolbar menu hides.

Categories

(Core :: Layout, defect)

Unspecified
Android
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: petru, Unassigned)

References

(Blocks 1 open bug, )

Details

(Whiteboard: [geckoview:toolbar])

From github: https://github.com/mozilla-mobile/fenix/issues/16298.

Steps to reproduce

Navigate to https://www.sleeping.pt/wp/2020/08/22/test-parallax-cover/

Watch the following video that shows the problem.
https://www.sleeping.pt/wp/wp-content/uploads/2020/10/2020_10_30_21_58_13-2.webm

Expected behavior

Whenever the toolbar disappears, redraw the background image.

Actual behavior

The background image is not redrawn.

Device information

  • Android device: Galaxy A20e
  • Fenix version: 82.1.1

Change performed by the Move to Bugzilla add-on.

:hiro can you investigate?

Flags: needinfo?(hikezoe.birchill)
Whiteboard: [geckoview:toolbar]

It seems Chrome does "layout" (reflow in our words) when the toolbar is completely hidden? (IIRC I commented somewhere in b.m.o I was suspecting Chrome does re-layout when the toolbar is hidden, whereas we just change the return value of window.innerHeight).

Anyway, this needs investigations in Chrome what they do exactly.

Also note that, fwiw, I can't reproduce the issue on https://www.sleeping.pt/wp/2020/08/22/test-parallax-cover/.

Flags: needinfo?(hikezoe.birchill)
Summary: [Bug] Background images are not fully rendered when the tollbar menu hides. → [Bug] Background images are not fully rendered when the toolbar menu hides.
Component: General → Layout
Product: GeckoView → Core
Severity: -- → S3
See Also: → 1739323

Closing this bug as incomplete because the test pages in comment 0 and comment 2 are now 404, so we have no way to test. Fortunately, the test case in similar bug 1739323 is still available and I can reproduce that bug in Fenix 100.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.