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 11989 - Not validated CSS3 vendor-specific prefixes, like -webkit-, -moz-, -o- etc.
Summary: Not validated CSS3 vendor-specific prefixes, like -webkit-, -moz-, -o- etc.
Status: RESOLVED FIXED
Alias: None
Product: CSSValidator
Classification: Unclassified
Component: CSS 3 (show other bugs)
Version: CSS Validator
Hardware: All All
: P2 major
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: qa-dev tracking
URL: none -- offline webpage
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-05 22:14 UTC by Tiel
Modified: 2013-02-13 15:14 UTC (History)
1 user (show)

See Also:


Attachments

Description Tiel 2011-02-05 22:14:21 UTC
I am running Firefox 3.6.13 on Windows 7. I attempted to validate a CSS3 document and it yielded this response: 

13 	#name 	Property -webkit-transform doesn't exist : rotate(90deg) rotate(90deg)
14 	#name 	Property -moz-transform doesn't exist : rotate(90deg) rotate(90deg)
15 	#name 	Property -o-transform doesn't exist : rotate(90deg) rotate(90deg) 

These were the lines it was referring to:

	-webkit-transform: rotate(90deg); 
	-moz-transform: rotate(90deg);	
	-o-transform: rotate(90deg);

The document works perfectly to transform text in the version of Firefox that I'm using. I re-checked the syntax and values of the statements but according to the CSS3 tutorial on the w3schools.com website (http://w3schools.com/css3/css3_pr_transform.asp), the code was valid. 

I am not aware of whether this is a new bug or not.
Comment 1 Binyamin 2011-02-11 12:18:02 UTC
Hi Tiel!

How much I know, W3C CSS3 standards does not accept vendor-specific prefixes (like this are -webkit-*, -moz-*, -o-*, -khtml-*, -ms-*), so it'll not be valid by http://jigsaw.w3.org/css-validator/ CSS3 validating.

So `transform:scale(1.2);` will be returned valid.
Comment 2 Tiel 2011-02-11 17:25:11 UTC
(In reply to comment #1)
> Hi Tiel!
> 
> How much I know, W3C CSS3 standards does not accept vendor-specific prefixes
> (like this are -webkit-*, -moz-*, -o-*, -khtml-*, -ms-*), so it'll not be valid
> by http://jigsaw.w3.org/css-validator/ CSS3 validating.
> 
> So `transform:scale(1.2);` will be returned valid.

Thanks for your reply! I just tried the validator (I made sure to set it to CSS 3) with this example:

================================================================================
#box {
   transform: rotate(30deg);
}
================================================================================

Unfortunately, I received an error on it! This is what I was talking about in my bug report, though. I specifically went to w3schools (http://www.w3schools.com/css3/css3_2dtransforms.asp) and took the non-browser-specific example to use and it was the exact one that received the error.

================================================================================
2 	#box 	Property transform doesn't exist : rotate(30deg) rotate(30deg) 
================================================================================

I then tried the example given on the w3schools link that I mentioned above and received an error for every line. Note I copied it with copy and paste. There was no error with formatting so it wasn't some copy/paste issue. I believe the validator just doesn't recognize it properly yet. Even if it's just browser-specific, it should be more of a warning than an error but since it shows it on the w3schools page itself, you'd think it would be more intuitive than to just show an error with everything.

This may seem like no big deal (and surely it really is nothing consequential to most people -- especially considering CSS3 is so new) but there are individuals that require this for educational purposes. My class, for example, needs to validate all of their work using the validator and it creates an issue if warnings or errors are given for valid CSS.
Comment 3 Binyamin 2011-02-15 10:52:45 UTC
Seems like W3C CSS Validator (CSS level 3) actually has no CSS3 assigned.