New issue
Advanced search Search tips

Issue 618801 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

testRunner.capturePixelsAsyncThen() captures wrong bitmap if called multiple times with composited scrolling

Project Member Reported by wangxianzhu@chromium.org, Jun 9 2016

Issue description

1. Modify LayoutTests/fast/scrolling/background-paint-composited-scrolled.html by replacing runAfterLayoutAndPaint to testRunner.capturePixelsAsyncThen():

testRunner.capturePixelsAsyncThen(function() {
  var container = document.querySelector('#container');
  var box = document.querySelector("#box");
  container.scrollTop = 400;
  box.style.backgroundColor = "green";
  testRunner.capturePixelsAsyncThen(function() {
    container.scrollTop = 0;
    if (window.testRunner)
      testRunner.notifyDone();
  });
});

2. Run the test: run-layout-tests fast/scrolling/background-paint-composited-scrolled.html

The test fails because the final captured image (the one captured by test_runner at the end of the test) is the image when container.scrollTop was 400, not the final state.

If add another capturePixelsAsyncThen:

testRunner.capturePixelsAsyncThen(function() {
  var container = document.querySelector('#container');
  var box = document.querySelector("#box");
  container.scrollTop = 400;
  box.style.backgroundColor = "green";
  testRunner.capturePixelsAsyncThen(function() {
    container.scrollTop = 0;
    testRunner.capturePixelsAsyncThen(function() {
      testRunner.notifyDone();
    });
  });
});

The test still fails but the captured image is weird: the contents are in correct final status, but the scrollbar is still in status when container.scrollTop was 400.

Checked display items at blink side and they all seem correct.

The test passes with threaded-compositing enabled, which might indicate that we have some synchronization issues about composited scrolling in single-threaded compositing mode.
 
Project Member

Comment 1 by sheriffbot@chromium.org, Jun 12 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 2 by enne@chromium.org, Jun 12 2017

Status: Available (was: Untriaged)
Seems like this is likely still a bug.  I don't know that I'll have time to look into it though, sorry.
Project Member

Comment 3 by sheriffbot@chromium.org, Jun 13 2018

Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by samans@chromium.org, Jun 22 2018

Cc: danakj@chromium.org piman@chromium.org vmp...@chromium.org
Status: Available (was: Untriaged)
Adding more cc owners.

Sign in to add a comment