TD doesn't show border if it has position relative and table has border collapse (Rendering issue)
Reported by
raduanas...@gmail.com,
Apr 25 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.87 Safari/537.36 Steps to reproduce the problem: 1. See the fiddle at https://jsfiddle.net/raduanastase/4jpte1ka/ 2. Or create a table with border-collapse: collapse; 3. Add border bottom and position relative to td tag. What is the expected behavior? The border should be visible. What went wrong? The border isn't shown. Did this work before? Yes Versions < 50 Chrome version: 50.0.2661.87 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 21.0 r0 If you toggle the "position: relative" rule from dev tools, it's shown correctly.
,
Apr 25 2016
If someone needs a workaround/hack, you could add 'position: static' to one of the td-s and the border will be shown.
,
Apr 26 2016
It looks like the problem is OS independent, confirmed that this behavior also occurs in Chrome version 50.0.2661.86 on Ubuntu 14.04 and Yosemite
,
May 5 2016
I am experiencing this issue also, system details below. I don't admin this machine so not sure when Chrome was last updated, however as a user it seems to have been a recent regression. Chrome Version: 50.0.2661.94 (Official Build) (64-bit) Revision: 0c319c380220abe3daf0277e40a2d0b22a7c4550-refs/branch-heads/2661@{#645} OS: Mac OS X Yosemite 10.10.5 User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36
,
May 17 2016
Expanding on https://bugs.chromium.org/p/chromium/issues/detail?id=606351#c2 , you can also just add: table:after { content: ' '; display: table-cell; } Fiddle demonstrating the existence of a static td somehow fixes the issue: http://jsfiddle.net/et1su5dp/5/
,
May 17 2016
Thanks for this fix. I used
table:after {
content: '';
display: table-cell;
}
to fix my issue.
,
Sep 11 2016
This seems to have been fixed. On Chrome 53.0.2785.101, my test case now renders correctly.
,
Sep 12 2016
I can confirm that. On my 52.0.2743.116 works fine now.
,
Sep 12 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by raduanas...@gmail.com
, Apr 25 2016392 bytes
392 bytes View Download