This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 3300 - Border Shorthand not recorgnized as valid
Summary: Border Shorthand not recorgnized as valid
Status: RESOLVED INVALID
Alias: None
Product: CSSValidator
Classification: Unclassified
Component: text area (show other bugs)
Version: CSS Validator
Hardware: PC Windows XP
: P2 minor
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
URL: http://programmers.cpcug.org/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-23 11:54 UTC by Thomas Miller
Modified: 2007-07-19 09:27 UTC (History)
0 users

See Also:


Attachments

Description Thomas Miller 2006-05-23 11:54:30 UTC
Not sure which version of the validator is being used.  I use the botton on the page being validated.

border:'2' 'groove' '#000066';

Returns this error

Line: 128 Context : .TableCalender

Invalid number : border '2' is not a border-color value : '2' 'groove' '#000066' 

Yet the documentation says

'border'
    Value:  	[ <'border-width'> || <'border-style'> || <color> ] | inherit
    Initial:  	see individual properties
    Applies to:  	all elements
    Inherited:  	no
    Percentages:  	N/A
    Media:  	visual
Comment 1 Bj 2006-05-23 16:33:44 UTC
If you put something into ' characters, you have a string, not a keyword, color value, or length, and without the ' characters, 2 would not be valid as you have to use a length and lengths have to have a unit identifier.
Comment 2 Thomas Miller 2006-05-23 18:36:19 UTC
It turns out that I had my syntax wrong.  The error message received was not appropriate to the problem.  Also, please add an example to the help that uses real values.  This would have solved my problem much quicker.  "||" in SQL means to concatinate together.  An example like this

border: 2px groove #000066;

would have solved the problem much quicker.

By the way I had 

border:  '2px' 'groove' '#000066';
Comment 3 Olivier Thereaux 2007-07-19 09:27:25 UTC
closing as "not a bug", even though it is acknowledged that the error message could be less confusing.