Bug 17562

Summary: child table column has no background color because parent table height is not defined
Product: WebKit Reporter: jasneet <jasneet>
Component: TablesAssignee: Nobody <webkit-unassigned>
Status: NEW ---    
Severity: Normal CC: ahmad.saleem792, anantha, ap, bfulgham, gsherloc, rniwa, simon.fraser, zalan
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Windows XP   
URL: https://www209.americanexpress.com/merchant/singlevoice/USEng/FrontServlet?request_type=navigate&page=processingMain&merch_ne=ProcSuppl_GreenBar
Attachments:
Description Flags
screenshot
none
reduction
none
Safari 15.6 matches Chrome but differs from Firefox none

Description jasneet 2008-02-26 16:37:20 PST 
I Steps:
Go to https://www209.americanexpress.com/merchant/singlevoice/USEng/FrontServlet?request_type=navigate&page=processingMain&merch_ne=ProcSuppl_GreenBar

II Issue: The leftmost blue column has white space

III Conclusion: The code has 2 tables. The parent  table has the blue border. Within one of the <td> of the parent table, there's another table with the cyan background. The issue here is that the <td> in the child table (red background) does not span the entire height of the parent table. This is because the height of the parent table is not defined even though the <td> of the parent table that contains the child table has a height defined (for this case 100%)

IV Other browsers: 
FF: ok
Opera: not ok
IE 7: ok

V Nightly tested: r30551
Comment 1 jasneet 2008-02-26 16:38:15 PST 
Created attachment 19387 [details]
screenshot
Comment 2 jasneet 2008-02-26 16:38:35 PST 
Created attachment 19388 [details]
reduction
Comment 3 Gavin Sherlock 2009-05-02 07:12:47 PDT 
This problem is still present in r43110 on Leopard
Comment 4 Ahmad Saleem 2022-08-14 04:22:00 PDT 
Created attachment 461618 [details]
Safari 15.6 matches Chrome but differs from Firefox

I am able to reproduce this bug in Safari 15.6 on macOS 12.5 where Safari does not fill "red" to fill cell similar to Chrome but Firefox does. I am not sure on web-spec, what is right behavior. So I will leave others to conclude on this but just wanted to share updated testing results. Thanks!