On Tue, Aug 16, 2011 at 1:26 AM, jidanni@jidanni.org wrote:

Unknown property 'zoom'.  Declaration dropped. @ http://transgender-taiwan.org/load.php?debug=false&lang=zh-tw&module... Expected declaration but found '*'.  Skipped to next declaration. @ http://transgender-taiwan.org/load.php?debug=false&lang=zh-tw&module... Expected 'important' but found 'ie'.  Expected ';' or '}' to terminate declaration but found 'ie'.  Declaration dropped. @ http://transgender-taiwan.org/load.php?debug=false&lang=zh-tw&module... Error in parsing value for 'list-style-type'.  Declaration dropped. @ http://transgender-taiwan.org/load.php?debug=false&lang=zh-tw&module... Unknown pseudo-class or pseudo-element '-webkit-input-placeholder'.  Ruleset ignored due to bad selector. @ http://transgender-taiwan.org/load.php?debug=false&lang=zh-tw&module...

Yeah, those happen. They're harmless, though. What happens is that we use browser-specific CSS hacks (in the !ie case) or vendor-specific CSS rules (in the -webkit case) or CSS3 stuff that some browsers don't understand yet (I suspect that's what's going on with zoom and list-style-type), and those things either aren't valid CSS or aren't expected/known by all browsers. But browsers just ignore stuff they don't understand, output a warning, and move on.

So these warnings are harmless and a testament to the fact that you can't write stuff that works in all browsers AND validates in all browsers (not 'validates' in the W3C sense, but 'validates' in the browser-doesn't-complain sense). We're in the situation where things work in all browsers but nearly all browsers complain about certain things (but only in the developer console, and without actually breaking functionality), and I think that's better than having a warning-free but broken (or less feature-rich) web site :)

Roan