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

Request #1749 Add support for <optgroup> element for multi-level arrays
Submitted: 2004-06-30 11:47 UTC
From: mvl22 at mailinator dot com Assigned: cweiske
Status: Closed Package: HTML_Select
PHP Version: Irrelevant OS: n/a
Roadmaps: (Not assigned)    
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 : 45 - 28 = ?

 
 [2004-06-30 11:47 UTC] mvl22 at mailinator dot com
Description: ------------ <optgroup> would be very useful for representing multidimensional arrays in a select. http://www.w3schools.com/tags/tag_optgroup.asp has further info on the <optgroup> tag. Reproduce code: --------------- n/a Expected result: ---------------- n/a Actual result: -------------- n/a

Comments

 [2004-07-11 22:10 UTC] gurugeek
Dear Maintainer, Your package html_select has currently 1 open bug. We urge you to take the necessary steps to solve the reported issues at your soonest convenience. If the bug issue hasn’t been addressed yet you are kindly asked to take the necessary steps to ensure a prompt resolution of the problem. If you already addressed the reported problem feel free to change the bug status as soon as possible. Regards David Costa PEAR Quality Assurance pear-qa@lists.php.net
 [2004-09-03 15:22 UTC] thesaur
Would you like to maintain this package? it is looking for some love. I only picked it up to make the release.
 [2010-02-14 19:16 UTC] cweiske (Christian Weiske)
-Status: Open +Status: Closed -Assigned To: +Assigned To: cweiske
This bug has been fixed in SVN. 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. Will be in 1.3.0