7388 2009-08-20 16:56:09 +0000 CSS3 properties are not recognized: zoom, word-wrap 2012-09-21 15:08:50 +0000 1 1 1 Unclassified CSSValidator CSS 3 CSS Validator PC Windows XP RESOLVED FIXED P2 normal --- 1 james dave.null caribou esnyder jukka.k.korpela rthawkcom www-validator-cvs oldest_to_newest 26566 0 james 2009-08-20 16:56:09 +0000 Description: The zoom and word-wrap properties of CSS3 are not recognized by the validator. This affects both the main validator and the dev version at http://qa-dev.w3.org:8001/css-validator/. Steps to reproduce: Enter by direct input the following CSS: a { zoom: 1; } a { word-wrap: break-word; } Actual Results: Neither zoom and word-wrap are recognized as CSS level 3 properties. Expected Results: They should both validate. Zoom is defined in: http://www.w3.org/TR/css3-transitions/#properties-from-css- Word-wrap is defined in: http://www.w3.org/TR/css3-text/#word-wrap 26567 1 james 2009-08-20 16:58:24 +0000 Hmm.. the link: http://www.w3.org/TR/css3-transitions/#properties-from-css- should include the trailing hyphen as part of the anchor. 60970 2 rthawkcom 2011-12-05 20:14:28 +0000 Over 2 years and it still isn't fixed! Seriously!? 69660 3 esnyder 2012-07-05 18:21:22 +0000 (In reply to comment #2) > Over 2 years and it still isn't fixed! Seriously!? I'm waiting for an explanation too. 'overflow-wrap' errors out the exact same way as word-wrap. 73690 4 jukka.k.korpela 2012-09-12 08:26:44 +0000 The zoom property is an IE feature (now adopted by WebKit too). Though it was once mentioned in a CSS3 WD, it no more is. So this part of the bug report should be closed as "not a bug". The word-wrap property is now recognized in CSS 3 mode, despite being only in a WD level document. However, the validator silently changes it to the currently recommended name: Valid CSS information a { overflow-wrap : break-word; } Apart from the question whether a warning should be issued in such a case, this part of the bug report could be closed as "fixed". 74226 5 caribou 2012-09-21 15:08:50 +0000 I mark this bug resolved-fixed. Thanks