Bug 202885

Summary: Pseudo-elements not treated as ASCII case-insensitive
Product: WebKit Reporter: Gô Shoemake <go.shoemake>
Component: CSSAssignee: Ryosuke Niwa <rniwa>
Status: RESOLVED FIXED    
Severity: Normal CC: ahmad.saleem792, ap, bfulgham, cdumez, koivisto, rniwa, simon.fraser, vitor.roriz, webkit-bug-importer, zalan
Priority: P2 Keywords: GoodFirstBug, InRadar
Version: Safari Technology Preview   
Hardware: Mac   
OS: macOS 10.15   

Gô Shoemake
Reported 2019-10-12 15:45:12 PDT
CSS Selectors 4 <https://drafts.csswg.org/selectors-4/#pseudo-element-syntax> clearly states: > Pseudo-element names are ASCII case-insensitive. CSS Selectors 4 is currently an Editor's Draft. But CSS 2.1 <https://www.w3.org/TR/CSS21/selector.html#pseudo-elements> also clearly states: > Pseudo-element and pseudo-class names are case-insensitive. Nevertheless, the following code does not have the expected effect: <!DOCTYPE html> <style> body::before { content: "Failure!" } body::BEFORE { content: "Success!" } </style> (As a data: URI for quick testing: data:text/html,<!DOCTYPE html><style>body::before{content:"Failure!"}body::BEFORE{content:"Success!"}</style> ) Related to Bug 81752, but I'm filing this separately since that bug seems focused on selectors determined by the host language (e.g., attribute selectors), and not selectors defined by CSS.
Attachments
Ahmad Saleem
Comment 1 2022-08-20 17:03:32 PDT
I turned the test case from Comment 0 into JSFiddle: Link - https://jsfiddle.net/fwzd8cu6/show I am able to reproduce this bug in Safari 15.6.1 and Safari Technology Preview 151 using above and it shows "FAILURE" while in case of other browsers (Chrome Canary 106 and Firefox Nightly 105) show "SUCCESS". Thanks!
Ryosuke Niwa
Comment 2 2022-08-20 22:56:56 PDT
EWS
Comment 3 2022-08-21 12:03:38 PDT
Committed 253631@main (2f1268f7d8b2): <https://commits.webkit.org/253631@main> Reviewed commits have been landed. Closing PR #3511 and removing active labels.
Radar WebKit Bug Importer
Comment 4 2022-08-21 12:04:16 PDT
Note You need to log in before you can comment on or make changes to this bug.