Bug 53498 - WebKit incorrectly calculates element basline when useing "display:inline-block" and "overflow: hidden"
Summary: WebKit incorrectly calculates element basline when useing "display:inline-blo...
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-01 09:04 PST by Berend-Jan Wever
Modified: 2022-07-27 14:25 PDT (History)
5 users (show)

See Also:


Attachments
Repro (435 bytes, text/html)
2011-02-01 09:04 PST, Berend-Jan Wever
no flags Details
Safari 15.6 matches with other browsers (658.27 KB, image/png)
2022-07-27 13:17 PDT, Ahmad Saleem
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Berend-Jan Wever 2011-02-01 09:04:17 PST
Created attachment 80763 [details]
Repro

I found a bug that leads to elements getting the wrong baseline when using CSS style "display:inline-block; overflow:hidden". I've attached a repro, which renders differently in FF and WebKit. At first I thought this was a bug in Firefox, but apparently this is by design and WebKit is wrong:
https://bugzilla.mozilla.org/show_bug.cgi?id=615712

In the attached repro, the first fieldset should apparently have the "2" aligned to the bottom to follow the spec. In Chrome and Safari this is not the case; both are aligned at the top.
Comment 1 Berend-Jan Wever 2011-02-02 05:13:59 PST
Quoting Ian Hickson "the right behaviour is the Gecko/Opera behaviour (a red box with a green box inside it, the green box being offset slightly so that vertically from the bottom there's a red line, a gap, a green line, the word "HTML5" crossed out by a red line, and then above that another green line). WebKit (Safari/Chrome) is wrong (it doesn't reset the inline-block baseline to the bottom of the line box due to the 'overflow' property as the current revision of the CSS level 2 spec requires in the last paragraph of section 10.8.1)."
Comment 2 Darth 2011-02-09 00:28:12 PST
This seems a duplicate of Bug 36084
Comment 3 Ahmad Saleem 2022-07-27 13:17:09 PDT
Created attachment 461258 [details]
Safari 15.6 matches with other browsers

I am unable to reproduce this bug using attached repo in Safari 15.6 on macOS 12.5 and as can be seen from attached screenshot, all browsers are matching with each other. Can we mark this as "RESOLVED CONFIGURATION CHANGED"? Thanks!