Closed Bug 271916 Opened 21 years ago Closed 21 years ago

Parsing negation selector should skip whitespace in more places? (ParseNegatedSimpleSelector)

Categories

(Core :: CSS Parsing and Computation, defect)

defect
Not set
minor

Tracking

()

RESOLVED FIXED

People

(Reporter: MatsPalmgren_bugz, Assigned: MatsPalmgren_bugz)

References

Details

(Keywords: css3, testcase)

Attachments

(3 files)

Parsing negation selector should skip whitespace in more places? (followup from bug 265542) ------- Additional Comment #21 From David Baron 2004-11-15 16:39 PDT [reply] ------- I'm wondering if ParseNegatedSimpleSelector needs to pass aSkipWS as PR_TRUE in some places...
Attached file Testcase #1
The relevant grammar is (http://www.w3.org/TR/css3-selectors/#grammar): functional_pseudo : FUNCTION S* [ IDENT | STRING | NUMBER | expression | negation_arg ] S* ')' ; {ident}"(" {return FUNCTION;}
Keywords: testcase
So it looks like we should also allow leading space after the '('
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: css3
Attached patch Patch rev. 1Splinter Review
Let me check the other FUNCTIONs first...
Assignee: dbaron → mats.palmgren
Attached file Testcase #2
Attachment #167242 - Flags: superreview?(dbaron)
Attachment #167242 - Flags: review?(dbaron)
Attachment #167242 - Flags: superreview?(dbaron)
Attachment #167242 - Flags: superreview+
Attachment #167242 - Flags: review?(dbaron)
Attachment #167242 - Flags: review+
Checked in 2004-11-28 07:04 PDT. -> FIXED
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: