New issue
Advanced search Search tips

Issue 860470 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Jul 10
Cc:
susan.boorgula@chromium.org
style-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

css grid the on setting column width to 0px child domNodes size not properly calculated when its width is set to auto

Reported by kamineni...@gmail.com, Jul 5 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Steps to reproduce the problem:
1. use css display:grid to layout Children
2. set the children domNode width:auto and height:auto  
3. set the first column with to 0px -> grid-template-columns: 0px 10px 50px 10px 50px;
4) I can still see the child node 

See the attached codepan page. set the grid-templeted-columns: 0px 10px 50px;

https://codepen.io/kkaminen/pen/vrQPZM

What is the expected behavior?
The child component should not be visible as we set the column width to 0px and its parent is set to 0px

What went wrong?
The css calculation for the width is wrong when used width:auto for the children when places inside the grid. 

This happen only when is change the column width after rendering. 

Did this work before? Yes 65

Does this work in other browsers? Yes

Chrome version: 67.0.3396.99  Channel: stable
OS Version: OS X 10.13.4
Flash Version:
Screen Shot 2018-07-05 at 7.44.16 AM.png
3.8 KB View Download

Comment 1 by krajshree@chromium.org, Jul 5

Labels: Needs-Bisect Needs-Triage-M67

Comment 2 by susan.boorgula@chromium.org, Jul 6

Cc: susan.boorgula@chromium.org
Labels: Triaged-ET Needs-Feedback
kaminenikvs@ Thanks for the issue.

Able to reproduce Mac OS 10.13.3, Windows 10 and Ubuntu 14.04 on the reported version 67.0.3396.99, but the issue is fixed on the latest Beta 68.0.3440.42 by following the steps given above.
Attached is the screen cast for reference.

Request you to please check and confirm if the issue is reproducible on latest Beta 68.0.3440.42, as Stable 67.0.3396.99 will be moved to M68 tentatively in 2 weeks.

Thanks..
860470-M68.mp4
676 KB View Download

Comment 3 by kamineni...@gmail.com, Jul 6 

I did verified in Chrome Version Beta 68.0. and i dont see the issue. Thank you for the prompt response
Project Member

Comment 4 by sheriffbot@chromium.org, Jul 6

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

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

Comment 5 by susan.boorgula@chromium.org, Jul 9

Labels: Needs-Feedback
kaminenikvs@ Thanks for the update.

As per comment #3, can you please confirm if this issue can be closed, as the issue is fixed on the latest Beta 68.0.3440.42.

Thanks..

Comment 6 by kamineni...@gmail.com, Jul 9 

Yes i confirm that i dont see the issue in Beta  68.0.3440.42.
Project Member

Comment 7 by sheriffbot@chromium.org, Jul 9

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

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

Comment 8 by susan.boorgula@chromium.org, Jul 10

Labels: -Needs-Bisect
Status: WontFix (was: Unconfirmed)
kaminenikvs@ Thanks for the update.

As per comment #6, closing this issue and marking this issue as WontFix as the issue is working fine in Beta 68.0.3440.42 and the reporter has confirmed the same.

Thanks..
►

Sign in to add a comment