Bug 19407

Summary: CSS3 Selector Test: *= ~= ^= $= should all accept the empty string, but match nothing
Product: WebKit Reporter: Robert Blaut <webkit>
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: VERIFIED FIXED    
Severity: Normal Keywords: HasReduction
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
URL: http://disruptive-innovations.com/zoo/css3tests/selectorTest.html#target
Attachments:
Description Flags
minimal test case
none
fix for the bug reflecting the latest CSS WG decision darin: review+

Description Robert Blaut 2008-06-06 05:49:54 PDT
The issue appeared after decision of CSS WG: http://lists.w3.org/Archives/Public/www-style/2008Apr/0038.html

Attribute Selectors
-------------------

   RESOLVED: Copy attribute selector wording from Selectors into CSS2.1 to
             resolve incompatibility.
   RESOLVED: *= ~= ^= $= all accept the empty string, but match nothing.
             Note that this overrides a previous resolution which stated
             that such attribute selectors are invalid.
   RATIONALE: These selectors are meaningless. This resolution matches
              existing implementations for ~=, which was introduced in
              CSS2.1, and makes *=, ^=, and $=, which were introduced in
              Level 3,
   [note, see also http://lists.w3.org/Archives/Public/www-style/2008Apr/0021.html  which was posted in response to this]
Comment 1 Robert Blaut 2008-06-06 05:50:53 PDT
Created attachment 21525 [details]
minimal test case
Comment 2 Robert Blaut 2008-06-06 05:53:26 PDT
Created attachment 21526 [details]
fix for the bug reflecting the latest CSS WG decision
Comment 3 Darin Adler 2008-06-06 09:21:19 PDT
Comment on attachment 21526 [details]
fix for the bug reflecting the latest CSS WG decision

r=me
Comment 4 Mark Rowe (bdash) 2008-06-06 15:52:21 PDT
Landed in r34409.