[TYPO3-core] RFC: XHTML and accessibility ofFORM cObj(#1369) [wrong patchfile!]

Martin Kutschker Martin.Kutschker at blackbox.net
Thu Nov 24 09:37:30 CET 2005

Sebastian Kurfuerst <sebastian at garbage-group.de> writes on 
Wed, 23 Nov 2005 19:52:04 +0100 (MET):

> Hi,

The JS-code is slightky misleading:

var formname = document[theFormname];

formname is assigned the form object, not it's name.

I know it's nitpicking, but it's irritating when name and content obviously mismatch.

> > The description says in xhtml strict mode name is replaced with id
> > inthe form tag. From the patch it looks like it is always changed.
> Yes, but this doesn't break backwards-compatibility, does it?

It may well be that it does. Why break some stupid browsers, just because of this xhtml crave? <rant>I really like standards, but I begin to hate XHTML 1.1. What has been gained by removing the name attribute?</rant>

I see no point in breaking the page for some users when we can fix it by using id only for "progressive" xhtml versions. If I stick to old html standards I expect that TYPO3 delivers "old" code.


More information about the TYPO3-team-core mailing list