Table cell borders appear in the wrong place after rotating the phone
Reported by
nanshan...@gmail.com,
Jul 17 2016
|
|||||||||||||||||
Issue descriptionExample URL: Steps to reproduce the problem: 1. Open the attatched example.html on a phone 2. Rotate the phone What is the expected behavior? Cell borders in around the content What went wrong? Borders appear in a strange location Does it occur on multiple sites: N/A Is it a problem with a plugin? N/A Did this work before? N/A Does this work in other browsers? Yes Chrome version: 51.0.2704.81 Channel: stable OS Version: 6.0.1 Flash Version: It can also be reproduced by using device toolbar in desktop Chromium Developer Tools
,
Jul 22 2016
Issue reproducible, tested on Samsung Galaxy S5/6.0.1, Nexus 5X/6.0.1. Logcat @ http://go/chrome-androidlogs1/6/628930
,
Jul 25 2016
This is not IO>DeviceOrientation (which has to do with api for sensors); it looks like this has more to do with blink layout/css rendering. adding cc:pdr@ maybe he can route this bug more appropriately.
,
Jul 25 2016
I think this is a layout bug in how we calculate the cell border position. Can we get a bisect of this? To reproduce: 1) Open example.html 2) Open the inspector, enable the mobile device mode 3) Click the rotate button and switch from portrait to landscape 4) Notice the table cell borders for "long string" and "another string" are not around the text but instead are offset.
,
Jul 26 2016
I have tried some old releases of Chrome Stable. The test case renders fine in 45.0.2454.94, but broken in 46.0.2490.76
,
Aug 10 2016
Hello. Just curious: Is anyone willing to take a look at this?
,
Aug 10 2016
Would someone be willing to bisect using instructions from comment #4?
,
Aug 19 2016
Reproducible on Nexus 6P / MTC20F. 45.0 2454.103 - good 46.0.2490.10 - bad No official builds between the two builds above.
,
Aug 31 2016
,
Sep 25 2016
Could somebody kindly investigate this?
,
Nov 10 2016
,
Jun 3 2017
This issue still exists in Chromium 58.0.3029.110
,
Jun 4 2018
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
,
Jun 4 2018
|
|||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||
Comment 1 by rsgav...@chromium.org
, Jul 21 2016