Closed
Bug 841983
Opened 12 years ago
Closed 12 years ago
require whitespace around 'and', 'or', and after 'not' in @supports rules
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
mozilla21
People
(Reporter: dbaron, Assigned: dbaron)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
7.18 KB,
patch
|
heycam
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Comment 1•12 years ago
|
||
Matches spec change in https://dvcs.w3.org/hg/csswg/rev/34b185ae3bac .
Attachment #714709 -
Flags: review?(cam)
Comment 2•12 years ago
|
||
Comment on attachment 714709 [details] [diff] [review]
Require whitespace around 'not', 'and', and 'or' keywords in @supports rules.
Review of attachment 714709 [details] [diff] [review]:
-----------------------------------------------------------------
r=me with that.
::: dom/locales/en-US/chrome/layout/css.properties
@@ +120,5 @@
> PEBadDirValue=Expected 'ltr' or 'rtl' in direction selector but found '%1$S'.
> PESupportsConditionStartEOF2='not', '(', or function
> PESupportsConditionInParensEOF=')'
> PESupportsConditionNotEOF='not'
> +PESupportsWhitespaceRequired=Expected whitespace after 'not', 'and', or 'or'.
This should be "Expected whitespace after 'not', or before and after 'and' or 'or'.", but that might be getting a bit confusing. Can you find some wording that captures the "white space after 'and' and 'or'" requirement too, or maybe split this into two separate error messages (one for "not" and another for "and" and "or")?
Attachment #714709 -
Flags: review?(cam) → review+
Assignee | ||
Comment 3•12 years ago
|
||
Except the way the code is structured, it'll never give that error before an 'and' or an 'or'; it'll just finish parsing the conjunction or disjunction and report the next thing as unexpected.
Comment 4•12 years ago
|
||
OK, fair enough. One other thing I was going to mention that I forgot to: can you update the comments above each of the Parse*() functions that have the grammar snippets in them to match what you are now parsing?
Assignee | ||
Comment 5•12 years ago
|
||
Comment 6•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → mozilla21
Assignee | ||
Updated•8 years ago
|
Blocks: css-conditional-3
You need to log in
before you can comment on or make changes to this bug.
Description
•