Bug 56994

Summary: :not should accept "a comma-separated list of compound selectors"
Product: WebKit Reporter: Ojan Vafai <ojan>
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: bdakin, benjamin, eric, hyatt, koivisto, simon.fraser, tkent, yuzo
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: OS X 10.5   
Attachments:
Description Flags
Patch none

Ojan Vafai
Reported 2011-03-23 21:14:12 PDT
http://dev.w3.org/csswg/selectors4/#negation This does mean we'll fail http://samples.msdn.microsoft.com/ietestcenter/css3/selectors/notSelectorSequence.htm, but I think it's better that we match the better behavior of the Selectors 4 spec. I'll try and find someone at Microsoft to see if they're willing to change the test.
Attachments
Patch (29.17 KB, patch)
2011-03-25 00:27 PDT, Ojan Vafai 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Ojan Vafai
Comment 1 2011-03-25 00:27:01 PDT
Created attachment 86903 [details] Patch
Ojan Vafai
Comment 2 2011-03-25 00:27:50 PDT
I've emailed Resig and MS to see if they're willing to change their tests to match the new spec.
Eric Seidel (no email)
Comment 3 2011-05-23 14:50:24 PDT
Any update? It's been about a month.
Adam Barth
Comment 4 2011-10-14 17:22:00 PDT
Comment on attachment 86903 [details] Patch Please re-nominate when you hear back from John.
Ojan Vafai
Comment 5 2012-01-05 17:01:19 PST
The Resig test suite appears to also live at http://dev.w3.org/2006/webapi/selectors-api-testsuite/, which covers selectors levels 2.1 and 3. And it's not clear who maintains it. This is changed in http://dev.w3.org/csswg/selectors4/, which does not have a test suite yet. Is anyone opposed to me committing this without getting this test suite updated since it's testing selectors 3 and the API change this implements is part of selectors 4 given that I can't get responses from Resig or MS?
Benjamin Poulain
Comment 6 2014-11-01 10:42:12 PDT
WebKit supports :not() of Level 4.
Note You need to log in before you can comment on or make changes to this bug.