Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.5.4

Bug #16357 Multiple equal complex at rules not parsed correctly
Submitted: 2009-06-21 17:58 UTC
From: torerikh Assigned: farell
Status: Closed Package: HTML_CSS (version 1.5.3)
PHP Version: 5.2.4 OS: Ubuntu
Roadmaps: 1.5.4    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 3 + 27 = ?

 
 [2009-06-21 17:58 UTC] torerikh (Tor-Erik Hagen)
Description: ------------ If multiple "equal" at rules are included in the css file, only the last is included in the parse result. Test script: --------------- $a = new HTML_CSS(null, null); $a->parseString(" @media print { body { font-size: 10pt } } @media screen { body { font-size: 10pt, font-weight: bold } } @media screen { body { font-size: 12pt } } ", true); print_r($a->_css); Expected result: ---------------- Two @media screen rules should be in the internal _css array or one rule with the content of the two from the css file merged. Actual result: -------------- Only the last @media screen rule is included in the internal _css array

Comments

 [2009-06-21 18:19 UTC] torerikh (Tor-Erik Hagen)
There is a slight mistake in the test script @media screen { body { font-size: 10pt, font-weight: bold } } should be: @media screen { body { font-size: 10pt; font-weight: bold; } } It does not, however, make any difference in the test result.
 [2009-06-21 23:56 UTC] farell (Laurent Laville)
-Status: Open +Status: Verified
 [2009-07-03 02:42 UTC] farell (Laurent Laville)
-Status: Verified +Status: Closed -Assigned To: +Assigned To: farell
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.