New issue
Advanced search Search tips

Issue 726801 link

Starred by 3 users

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Incorrect rounding vw and vh on gpu layers

Reported by ilordgu...@gmail.com, May 26 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce the problem:
1. Open https://jsfiddle.net/uvj89m0t/2/
2. Move the dividing line so that a white line appears under the block.

What is the expected behavior?
This line should not be there.

What went wrong?
If I understand correctly the elements specified in vh or vw units are not rounded correctly when rendered on a separate gpu layer. As a result, the elements that must be the same have different sizes.

Did this work before? No 

Does this work in other browsers? No
 The error also occurs in Firefox, but in Edge everything is working fine.

Chrome version: 58.0.3029.110  Channel: stable
OS Version: 10.0
Flash Version:
 
Screenshot_10.jpg
12.9 KB View Download
Components: -Blink>CSS Blink>Paint
I can reproduce on mac v58.
Is this a problem with paint rather than css?

Comment 2 Deleted

joelhockey@chromium.org, I'm not an expert, but everything is normal in the microsoft Edge. I'm sure that this line should not be.
Components: -Blink>Paint Blink>Compositing
Labels: BugSource-User PaintTeamTriaged-20170530 OS-Android OS-Chrome OS-Linux OS-Mac
Status: Available (was: Unconfirmed)
We're snapping the layer size differently than we snap the div element that contains it. The issue reproduces on any platform.

I guess this is a CompositedLayerMapping bug, because that's where we size the layers.
Project Member

Comment 5 by sheriffbot@chromium.org, May 31 2018

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.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Available (was: Untriaged)

Sign in to add a comment