Output Broken: Invalid Output (Error) on Dashboard: autocomplete and (Warning but more serious) name/id conflict

[hakre]

Dashboard output (admin backend) has at least an error. patched it.

[hakre]

dashboard errors

[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.

Having name != id is not a violation of any standard.

[sampablokuper]

Replying to 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>.

[azaozz]

Replying to sampablokuper:
It seems it's part of the things to come: ​http://www.whatwg.org/specs/web-apps/current-work/multipage/forms.html#attr-form-autocomplete

[sampablokuper]

Replying to azaozz:

Replying to sampablokuper:
It seems it's part of the things to come: ​http://www.whatwg.org/specs/web-apps/current-work/multipage/forms.html#attr-form-autocomplete

If/when WordPress starts using the HTML 5 doctype by default, then fine, use @autocomplete . In the meantime, it's invalid and needs patching.

Also, what about the <br /> I mentioned above?