TabChild::RecvUpdateDimensions trigger PresShell::ResizeReflowOverride all the time in B2G::reftest

RESOLVED INVALID

Status

()

RESOLVED INVALID
4 years ago
4 years ago

People

(Reporter: u459114, Assigned: u459114)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

4 years ago
In reftest, widget/window size keep still. Supposedly, we should only receive TabChild::RecvUpdateDimensions once in a whole test run. File this bug to dig out why reftest content receive this message from chrome all the time in B2G::reftest run
(In reply to C.J. Ku[:cjku] from comment #0)
> In reftest, widget/window size keep still. Supposedly, we should only
> receive TabChild::RecvUpdateDimensions once in a whole test run. File this
> bug to dig out why reftest content receive this message from chrome all the
> time in B2G::reftest run

Are you sure it's TabChild::RecvUpdateDimensions that triggered he resize reflow? Per bug 997101 comment 58 before-first-paint is sent for each reftest, maybe it's the reason.
(Assignee)

Comment 3

4 years ago
OK, then, everything make sense to me.

reftest-content sets fullZoom in onload event handler
http://dxr.mozilla.org/mozilla-central/source/layout/tools/reftest/reftest-content.js?from=reftest-content.js&case=true#592

Which may come later then first-paint, so we may receive two SetCSSViewport before or after SetFullZoom.

Close this one.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
(In reply to C.J. Ku[:cjku] from comment #3)
> OK, then, everything make sense to me.
> 
> reftest-content sets fullZoom in onload event handler
> http://dxr.mozilla.org/mozilla-central/source/layout/tools/reftest/reftest-
> content.js?from=reftest-content.js&case=true#592
> 
> Which may come later then first-paint, so we may receive two SetCSSViewport
> before or after SetFullZoom.
> 
> Close this one.

Thanks. The redundant SetCSSViewport is indeed a performance problem and we should fixed if we could know why the reftest failed in bug 997101.
You need to log in before you can comment on or make changes to this bug.