RESOLVED CONFIGURATION CHANGED 117359
tables with display:block layed out differently than other browsers
https://bugs.webkit.org/show_bug.cgi?id=117359
Summary tables with display:block layed out differently than other browsers
Alex Christensen
Reported 2013-06-07 13:05:24 PDT
Firefox and Opera (haven't tested IE) place the first cell data above the second cell data because it has display:block. WebKit places the first cell data to the left of the second cell data because it's in a table row. Which is correct? <html> <head> <style> td { display:block; } </style> </head> <body> <table> <tr> <td> first cell data </td> <td> second cell data </td> </tr> </table> </body> </html>
Attachments
Yuki Sekiguchi
Comment 1 2013-06-09 20:03:09 PDT
If you add doctype to this content, WebKit becomes same as Firefox.
Alex Christensen
Comment 2 2013-08-20 09:11:09 PDT
This doesn't seem to be a problem, then. Should I change the status to RESOLVED/WONTFIX?
Yuki Sekiguchi
Comment 3 2013-08-20 19:46:23 PDT
(In reply to comment #2) > This doesn't seem to be a problem, then. Should I change the status to RESOLVED/WONTFIX? Maybe, yes.
Deepak Mittal
Comment 4 2014-02-10 22:43:26 PST
The Reason is when we put the document tag in the test page then style.get().display() for HTMLTableCellElement will come as the BLOCK and due to that control will go inside if (!child->isTableCell()) in RenderTableRow.cpp file, and layout is the Block flow. So the row's comes one above the another due to blow flow. But when the doctype is not present in the page then style.get().display() for HTMLTableCellElement will come as the TABLE_CELL so control will not go inside if (!child->isTableCell()) in RenderTableRow.cpp file, and layout is the inline flow, so cell's are coming adjustment.
Ahmad Saleem
Comment 5 2022-10-22 02:29:05 PDT
All browsers (Safari 16, STP 156, Chrome Canary 109 and Firefox Nightly 108) are matching in this test case and "First Cell Data" is not left of other cell. Marking this as "RESOLVED CONFIGURATION CHANGED". Please reopen, if it is still reproducible. Safari Technology Preview has some Webkit Table related quirks removed so it might work better in Quirk mode cases such as this: JSFiddle link - https://jsfiddle.net/6b1prgaf/show
Note You need to log in before you can comment on or make changes to this bug.