Bug 47208

Summary: CSS 2.1 failure: before-content-display-* tests fail
Product: WebKit Reporter: Simon Fraser (smfr) <simon.fraser>
Component: Layout and RenderingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: ahmad.saleem792, ap, hyatt, rniwa, syoichi, zalan
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Bug Depends on:    
Bug Blocks: 47141    
Attachments:
Description Flags
before-content-display-007.htm
none
Safari 15.5 matches other browsers none

Description Simon Fraser (smfr) 2010-10-05 14:04:02 PDT
Created attachment 69838 [details]
before-content-display-007.htm

The follow tests fail:

html4/before-content-display-007	fail
html4/before-content-display-015	fail
Comment 1 Dave Hyatt 2011-03-11 12:27:14 PST
We pass 015.htm now.  We fail 007.htm because we need to implement baselinePosition for inline-tables.  It just falls through to RenderBlock's, which does not do the right thing.

CSS2.1 states that the baseline of an inline-table is the baseline of the first row of the table, so we need to just add a baselinePosition method that returns that.
Comment 2 Ahmad Saleem 2022-06-17 04:32:28 PDT
Created attachment 460295 [details]
Safari 15.5 matches other browsers

I am unable to reproduce this bug in Safari 15.5 on macOS 12.4 and it matches all other browsers as shown in the picture.

Appreciate if this can be marked as "RESOLVED CONFIGURATION CHANGED", if it was fixed along the way or "RESOLVED INVALID", if the test was fixed due to web-spec and it was failure because of it.

If I am testing incorrectly, please retest accordingly. Thanks!
Comment 3 zalan 2022-06-17 07:23:06 PDT
(In reply to Ahmad Saleem from comment #2)
> Created attachment 460295 [details]
> Safari 15.5 matches other browsers
> 
> I am unable to reproduce this bug in Safari 15.5 on macOS 12.4 and it
> matches all other browsers as shown in the picture.
> 
> Appreciate if this can be marked as "RESOLVED CONFIGURATION CHANGED", if it
> was fixed along the way or "RESOLVED INVALID", if the test was fixed due to
> web-spec and it was failure because of it.
> 
> If I am testing incorrectly, please retest accordingly. Thanks!
Thank you!