[wp-trac] [WordPress Trac] #10108: Invalid HTML in get_search_form()
WordPress Trac
wp-trac at lists.automattic.com
Mon Dec 21 08:24:18 UTC 2009
#10108: Invalid HTML in get_search_form()
-----------------------+----------------------------------------------------
Reporter: kchrist | Type: defect (bug)
Status: reopened | Priority: normal
Milestone: | Component: Validation
Version: 2.9 | Severity: normal
Resolution: | Keywords: needs-patch
-----------------------+----------------------------------------------------
Changes (by hakre):
* keywords: has-patch commit close html search templates => needs-patch
* version: 2.8 => 2.9
* component: Template => Validation
Comment:
I did a bit research:
Hey, we're tight on shedule, December 15th is the date of the
[http://www.w3.org/TR/wai-aria/ latest ARIA 1.0 draft].
This problem is not new, looks like the folks with the W3C validator do
already work on it. The following Blog Post is about that:
[http://www.paciellogroup.com/blog/?p=107 How Can I Validate (X)HTML +
ARIA?].
So this might be more or less something to be changed in the doctype and
the configuration of the validators used.
[http://www.w3.org/Style/customdtd Using a custom DTD is not suggested],
but I think W3C is a bit biased on this one :).
What I sometime did was to inject DTD into the XHTML document which is
possible. That configures the W3C validator to accept certain elements and
attributes which are not part of the linked documents DTD. As this is a
workaround for an upcomming XHTML+ARIA DTD I assume that this would be a
valid exception to "don't use custom DTDs".
--
Ticket URL: <http://core.trac.wordpress.org/ticket/10108#comment:10>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list