Bug 53587 - Draw borders around tables or not?
Summary: Draw borders around tables or not?
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows Vista
: P1 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2011-02-02 05:54 PST by Berend-Jan Wever
Modified: 2022-07-23 13:02 PDT (History)
8 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Berend-Jan Wever 2011-02-02 05:54:23 PST
Viewing the following HTML/CSS in various browsers yields varying results. Firefox and Opera seem to agree on the layout, so I assume WebKit and MSIE are doing it wrong.


H
T <span style="display:table; border: 5px solid red;"></span>
M <table style="border: 5px solid green;"></table>
L <table style="display:inline-block; border: 5px solid green;"></table>
5

WebKit draws a border around all empty tables, so you see a red and two green blocks between the letters "H T M L 5".
Firefox/Opera/MSIE do not render these borders; Firefox and Opera do render borders on a table element with its 'display' css style set to 'inline-block', so you see one green box between L and 5. MSIE doesn't render any borders and only shows the letters. In addition, MSIE ignores the 'display: table' style on a span and 'display: inline-block' style on a table, rendering both as if no 'display' style is applied.
Comment 1 Ahmad Saleem 2022-07-23 08:43:22 PDT
I am unable to reproduce this bug using attached test case mentioned in Comment 0, I changed it to following JS Fiddle:

Link - https://jsfiddle.net/0cjnk7x8/show

All browsers (Chrome Canary 106, Firefox Nightly 104 and Safari 15.6 on macOS 12.5) renders the test case same.

I think this can be marked as "RESOLVED CONFIGURATION CHANGED". Although, if I am testing incorrectly then please retest accordingly. Thanks!
Comment 2 Radar WebKit Bug Importer 2022-07-23 11:34:30 PDT
<rdar://problem/97488519>
Comment 3 Alexey Proskuryakov 2022-07-23 13:02:40 PDT
Looks like WebKit behavior didn't change, and Firefox changed. So INVALID is a slightly more accurate resolution.