Re: [css-d] Fwd: Re: Vendor-specific extensions: warnings, not errors

2011-01-26 Thread Lundgren, Chad
Hello, I'm glad to hear they are taking a better approach to vendor extensions. However, even the new validator still has some other CSS3-related issues. This rule (shortened down to a test case length): #top-navigation ul ul { box-shadow: 0px 3px 3px rgba(0,0,0,0.2); } produced the

Re: [css-d] Fwd: Re: Vendor-specific extensions: warnings, not errors

2011-01-26 Thread Philippe Wittenbergh
On Jan 27, 2011, at 4:51 AM, Lundgren, Chad wrote: However, even the new validator still has some other CSS3-related issues. This rule (shortened down to a test case length): #top-navigation ul ul { box-shadow: 0px 3px 3px rgba(0,0,0,0.2); } produced the really odd and

[css-d] Fwd: Re: Vendor-specific extensions: warnings, not errors

2011-01-25 Thread Philip Taylor (Webmaster, Ret'd)
This is possibly relevant to Nancy's more recent query : Philip and David, If it were a snake... fantastic, I didn't know that had been added. So in checking this out - what limits does it have? Are vendor prefixes supported like Webkit etc? Thanks, Nancy Philip Taylor

Re: [css-d] Fwd: Re: Vendor-specific extensions: warnings, not errors

2011-01-25 Thread Philip Taylor (Webmaster, Ret'd)
Sorry, attached message was lost in transit. Repeated below. Philip Taylor (Webmaster, Ret'd) wrote: This is possibly relevant to Nancy's more recent query : Philip and David, If it were a snake... fantastic, I didn't know that had been added. So in checking this out - what limits does it

Re: [css-d] Fwd: Re: Vendor-specific extensions: warnings, not errors

2011-01-25 Thread Nancy Seeger
Hi Philip, That works much better with vendor extensions, at least in my current instance. I'll keep using it - bookmarking. This really helps, thank you! Nancy On Jan 25, 2011, at 6:40 PM, Philip Taylor (Webmaster, Ret'd) wrote: Sorry, attached message was lost in transit. Repeated below.