Bug 104008 - box-shadows are not rendered on most table-* display elements
Summary: box-shadows are not rendered on most table-* display elements
Status: RESOLVED DUPLICATE of bug 44654
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-04 08:41 PST by nate
Modified: 2022-06-07 16:17 PDT (History)
6 users (show)

See Also:

Attachments
Demonstrates the lack of a shadow on various table-* elements. (453 bytes, text/html)
2012-12-04 08:41 PST, nate 		no flags Details
Safari 15.5 differs from other browsers (143.36 KB, image/png)
2022-06-07 14:43 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 nate 2012-12-04 08:41:43 PST 
Created attachment 177494 [details]
Demonstrates the lack of a shadow on various table-* elements.

CSS box-shadows do not render on elements with table-header-group, table-footer-group, table-row-group, or table-row display.
Comment 1 Ian O'Dea 2018-03-15 14:50:35 PDT 
Confirming that I can also reproduce this bug using this repro case, and attempting to bump it.
Comment 2 Ahmad Saleem 2022-06-07 14:43:50 PDT 
Created attachment 460072 [details]
Safari 15.5 differs from other browsers

I am able to reproduce this bug in Safari 12.4 on macOS 12.4 using attached test case. Please refer to attached screenshot for reference. Thanks!
Comment 3 Ryosuke Niwa 2022-06-07 14:49:32 PDT 
Confirmed this differs from other browsers.
Comment 4 Ahmad Saleem 2022-06-07 14:50:05 PDT 
Is it something related to this bug in Chrome? https://crbug.com/268950
Comment 5 Ryosuke Niwa 2022-06-07 14:52:46 PDT 
(In reply to Ahmad Saleem from comment #4)
> Is it something related to this bug in Chrome? https://crbug.com/268950

Could be!
Comment 6 Ryosuke Niwa 2022-06-07 16:17:50 PDT 

*** This bug has been marked as a duplicate of bug 44654 ***