New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 634016 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

CompositorWorker: use consistent units for scroll offset and transforms

Project Member Reported by majidvp@chromium.org, Aug 3 2016

Issue description

I think we are using two different units (physical pixels, and dip) for scroll offsets and transforms. This makes animations that correlate transform and scroll offsets brittle and impossible to do well.

For example load parallax example [1] in Chrome (with CW and threaded-scrolling flags). Run them under device emulation with different device-pixel-ratio and rate of parallax varies.

We should use a consistent unit here e.g., dips or CSS .


[1] https://github.com/flackr/compositor-worker/blob/gh-pages/parallax-static/parallax.html

 
I'm not seeing this issue. To make it easier to test, I added an element which is transformed to the exact scroll position and it seems to work (modulo jitter) on various device pixel ratios under device emulation mode: http://flackr.github.io/compositor-worker/parallax-static/parallax.html
Status: WontFix (was: Available)
Hmmm, I cannot reproduce this on latest Canary either. Odd but that is good.

Sign in to add a comment