House of Fusion
Search over 2,500 ColdFusion resources here
  
Home of the ColdFusion Community

Mailing Lists
Home /  Groups /  Cascading Style Sheets (CSS)

Mozilla CSS3 and the W3C validation

  << Previous Post |  RSS |  Tree View |  Sort Oldest First |  Subscribe to this Group Next >> 

Mozilla CSS3 and the W3C validation.

> I thought the browser specific '-moz' was considered good, standard Peter Boughton 01/22/2009 04:12 PM
So I have been playing with some of the few CSS3 tricks that are Ian Skinner 01/22/2009 03:59 PM

01/22/2009 04:12 PM
Author: Peter Boughton Short Link: http://www.houseoffusion.com/groups/css/thread.cfm/threadid:1826#5704 > I thought the browser specific '-moz' was considered good, standard > practice these days? Using browser specific anything is never good practise. Especially browser specific things that are named after a browser. Might be the only way to achieve something sometimes though, so... > And is there any simple trick that would allow me to keep the > functioning, Mozilla specific CSS3 features and still get a passing > validation from the W3C tool? Your main stylesheets should have the standards version only. Create [stylesheet-name].[browser]fix.css for any browser-specific fixes. (e.g. "main.css" has "main.iefix.css", "main.mozfix.css", etc.) Then, as browsers fix things, you can just reduce/remove the fix files whilst leaving your main stylesheets untouched.
01/22/2009 03:59 PM
Author: Ian Skinner Short Link: http://www.houseoffusion.com/groups/css/thread.cfm/threadid:1826#5703 So I have been playing with some of the few CSS3 tricks that are available in Mozilla browsers, such as the Corner Rounding: -moz-border-radius: 25px; property. This works a real treat, so then I took a gander at the W3C CSS validation tool but it does not like this property, as far as it is concerned it does not exist.  It would be happy with the generic 'border-radius' property, but no browser supports this, as far as I know. I thought the browser specific '-moz' was considered good, standard practice these days?  Is this just a case of the validation tool not properly recognizing this? And is there any simple trick that would allow me to keep the functioning, Mozilla specific CSS3 features and still get a passing validation from the W3C tool? Thanks Ian
<< Previous Thread Today's Threads Next Thread >>

Search css

September 01, 2014

<<   <   Today   >   >>
Su Mo Tu We Th Fr Sa
   1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30         

Designer, Developer and mobile workflow conference