- From: Alan Gresley <alan@css-class.com>
- Date: Wed, 12 Oct 2011 21:56:07 +1100
- To: François REMY <fremycompany_pub@yahoo.fr>
- CC: "L. David Baron" <dbaron@dbaron.org>, Peter Beverloo <peter@lvp-media.com>, Paul Irish <paul.irish@gmail.com>, www-style@w3.org
On 12/10/2011 6:43 AM, François REMY wrote: > To me, it seems like any error should be handled by having the API > return false. Are there any case where you would prefer doing > otherwhise? The main problem may rather be: How simple is it to catch > all CSS errors with a parser that has been made to overcome any error, > and not especially "throwing" or "notifying" about them. I think David is taking about CSS parsing (as per the normal parsing rules) within @-rules. Like so. http://css-class.com/test/css21testsuite/at-rule-022.xht http://css-class.com/test/css21testsuite/at-rule-023.xht http://css-class.com/test/css21testsuite/at-rule-026.xht Opera 11.50 matches 'at-rule-022' where IE9, Gecko, Webkit and Opera matches 'at-rule-023' and 'at-rule-026'. -- Alan Gresley http://css-3d.org/ http://css-class.com/
Received on Wednesday, 12 October 2011 10:56:39 UTC