Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.32.0
Bug #12910 Minor XHTML woes with pearweb
Submitted: 2008-01-15 06:38 UTC
From: doconnor Assigned: davidc
Status: Closed Package: pearweb (version CVS)
PHP Version: Irrelevant OS:
Roadmaps: 1.19.0    
Subscription  


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 : 45 + 24 = ?

 
 [2008-01-15 06:38 UTC] doconnor (Daniel O'Connor)
Description: ------------ There are many places in pearweb with minor xhtml validator issues. See also; bug 1589 Test script: --------------- Install https://addons.mozilla.org/en-US/firefox/addon/249 Switch it to 'SGML Parser' mode Navigate various areas of pearweb Expected result: ---------------- Valid xhtml Actual result: -------------- Invalid xhtml

Comments

 [2008-01-15 07:01 UTC] doconnor (Daniel O'Connor)
http://pear.php.net/packages.php http://pear.php.net/bugs/bug.php http://pear.php.net/group/ http://pear.php.net/accounts.php and http://pear.php.net/pepr/ Also all fail, which is probably around 50% of the links I randomly followed. I'd provide more patches but pearweb won't install :S
 [2008-01-23 18:48 UTC] davidc (David Coallier)
I fixed all mentionned (attached)
 [2008-03-23 06:16 UTC] doconnor (Daniel O'Connor)
A second round of minor patches to public_html/* and tests/* Makes use of script type="text/javascript"
 [2008-03-30 11:56 UTC] dufuz (Helgi Þormar Þorbjörnsson)
FYI we are going to focus on HTML5, hence the no doctype (as per the HTML5 spec)
 [2009-06-03 21:09 UTC] doconnor (Daniel O'Connor)
-Status: Assigned +Status: Closed
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.