[wp-trac] [WordPress Trac] #9427: Output Broken: Invalid Output (Error) on Dashboard: autocomplete and (Warning but more serious) name/id conflict

[WordPress Trac]

#9427: Output Broken: Invalid Output (Error) on Dashboard: autocomplete and
(Warning but more serious) name/id conflict
--------------------------+-------------------------------------------------
 Reporter:  hakre         |        Owner:  anonymous
     Type:  defect (bug)  |       Status:  reopened 
 Priority:  normal        |    Milestone:  2.9      
Component:  General       |      Version:           
 Severity:  normal        |   Resolution:           
 Keywords:  has-patch     |  
--------------------------+-------------------------------------------------
Changes (by sampablokuper):

 * cc: sam.kuper@… (added)
  * status:  closed => reopened
  * resolution:  wontfix =>
  * milestone:  => 2.9


Comment:

 Replying to [comment:1 azaozz]:
 > Perhaps the autocomplete="off" should go in the <form> element. It may
 not be accepted by the W3C but is the de-facto standard supported by
 almost all browsers.

 Leaving invalid (X)HTML in core !WordPress code is unacceptable, IMO. It
 means that plugin and theme developers, among others, can no longer use
 the W3C validator to check that their plugin/theme/etc isn't producing
 invalid (X)HTML at a glance: they instead have to look or parse through
 the validation results to see if the reported issues are due to core
 !WordPress files or not. What a pain. Consequently, I'm reopening this
 ticket.

 By the way, in !WordPress 2.8.6 the dashboard now additionally contains
 the following invalid markup:

 {{{
 <textarea class="comment" rows="3" cols="10">Hi, this is a comment.<br
 />To delete a comment, just log in and view the post&#039;s comments.
 There you will have the option to edit or delete them.</textarea>
 }}}

 That <br /> isn't permitted in <textarea>.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/9427#comment:3>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software