Summary: The table at the bottom of the news article in the bug URL is misdrawn in both shipping Safari and with ToT WebKit. Firefox 2.0.0.3 renders it correctly. Steps to reproduce: 1. Start Safari or WebKit. 2. Open the URL: http://www.cyclones.com/ViewArticle.dbml?DB_OEM_ID=10700&ATCLID=848024 3. Scroll down to the end of the article and observe the table. Expected results: The table should be rendered correctly (with columns wide enough to accommodate the text). Actual results: The table columns are not rendered wide enough to accommodate the text. Regression: This occurs with shipping Safari 2.0.4 (419.3) on Mac OS X 10.4.9 (8P135) as well as with a local debug build of WebKit r20738 with the aforementioned software. It is not a regression.
Created attachment 13974 [details] Test case The "border=1" is to see what should be happening; it's not necessary for the test case.
See also bug 7695.
FF, IE and Opera tables do not inherit the text-indent value from its parent. The attached test case has a negative text-indent set for <p> tag which is being inherited by the child table in case of Webkit. Thus the issue. Tables in case of other browsers never inherit text-indent from its parent. Not sure if its a good thing or not. Is there any spec which talks about this behavior ? Are we suppose to fix this bug ?
Created attachment 150599 [details] TestCase The attached test case tries to show case the difference in behavior of Webkit and other browsers with regards to tables inheriting text-indent from its parent.
> FF, IE and Opera tables do not inherit the text-indent value from its parent. I don't agree with this analysis. The <div> has text-indent set, yet all browsers indent the <p> too (you can even add new ones and they are indented) so there is some inheritance going on. Using the debugging tools on FF and Opera, I confirm that text-indent is inherited but that the rule doesn't apply. For FF (I haven't dug the other browsers), it comes from the UA stylesheet: http://mxr.mozilla.org/mozilla-central/source/layout/style/html.css#248 FF, IE and Opera behavior doesn't really make much sense here but must reflect some web-authors' need. If we are to fix this bug, we should bring this issue to the standards body first.
Created attachment 461645 [details] Safari 15.6 differs from other browsers but STP 151 does not have this issue I am able to reproduce this issue using both test cases in Safari 15.6 on macOS 12.5 but as can be seen from STP 151 reference that it does not have this issue anymore and also other test (screenshot not attached) also render similar to other browsers (Chrome Canary 106 and Firefox Nightly 105) fine on STP 151 compared to Safari 15.6. I am going to mark this as "RESOLVED FIXED" time being, appreciate if someone can find related commit to highlight on why this got fixed in STP 151. Thanks!