Bug 23008 - display:inline doesn't make <table> elements render inline
Summary: display:inline doesn't make <table> elements render inline
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows XP
: P2 Normal
Assignee: Nobody
URL: http://www.cssdesignpatterns.com/Chap...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-28 05:08 PST by mhstamate
Modified: 2022-09-20 06:53 PDT (History)
7 users (show)

See Also:

Attachments
Safari 15.6 differs from other browsers (1.49 MB, image/png)
2022-07-23 05:30 PDT, Ahmad Saleem 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mhstamate 2008-12-28 05:08:49 PST 
Tested on:
- Windows XP SP3
- Apple Safari for Windows 3.2.1 using the r39474 WebKit nightly build for
Windows from http://nightly.webkit.org/
- Intel P4 2.4 GHz CPU (single core)
- javascript is enabled

Description:
Trying to display a <table> element as an inline element by setting:
table { display:inline; }
does not work.

<table> is still rendered as a block element. Other browsers like Opera correctly display the table as an inline element.

A test case is available at http://www.cssdesignpatterns.com/Chapter%2004%20-%20BOX%20MODELS/Display/example.html

How it should look: http://www.postimage.org/image.php?v=Pq1jrE7i
How it looks on WebKit: http://www.postimage.org/image.php?v=aV1nY75i
Comment 1 gmtfn 2010-03-15 21:15:42 PDT 
Is this report about essentially the same problem that mine is: bug 21092?
Comment 2 Ahmad Saleem 2022-07-23 05:30:05 PDT 
Created attachment 461155 [details]
Safari 15.6 differs from other browsers

I am able to reproduce this bug using attached test case and as can be seen from attached screenshot, (strong) block is not appear on same position as other browsers (I put it in circle for highlight) in Safari 15.6 on macOS 12.5. For other browsers output, please refer to attached screenshot.

If I am testing incorrectly, please retest accordingly. Thanks!
Comment 3 Ahmad Saleem 2022-09-20 06:53:27 PDT 
I am not able to reproduce this bug in Safari 16 and it seems to work similar to the browser (Chrome Canary 108 and Firefox Nightly 107).

I am not sure on which commit fixed it but I will mark this as "RESOLVED CONFIGURATION CHANGED" and tag other Webkit Engineers for their input. Thanks!