[TYPO3-core] RFC: Fix bugs #3397 (submit as image) and #2938 (editIcons)

[Ernesto Baschny [cron IT]]

Martin Kutschker schrieb am 22.05.2006 20:22:

>> Other than that it is probably also a "backwards compatibility" issue if
>> you change this. TSref [1] documents the "image" property for the FORM
>> cObject as a "IMAGE (cObject)". This makes no real sense for a submit
>> button, but there might be people using properties from the IMAGE
>> cObject [2] that aren't present in a IMG_RESOURCE [3].
>>
>> I think only altText and titleText make sense here. You might want to
>> handle those specifically in this code fragment.

> I added support for "altText", "titleText" and "params". Does "if" make
> sense? I don't think so as none of the other field types are conditional.

True. And this never worked anyway (with the old "<img"-replacement
function), so I wouldn't bother adding it now.

> While checking the specs for alt/title on input elements I noticed that
> we do not support any of this attributes (directly):
> 
> disabled

I think this is only useful if you have some javascript that will
enable/disable fields depending on certain conditions. So not needed in
our rather static "FORM"s.

> tabindex

Our FORMs are always linear so no need for tabindexes.

> accesskey

This would be a very cool addition to the FORM generation code. Together
with support for <fieldset>s (patches are available!), this would get a
big +1 from the accessibility guys.

> onfocus
> onblur
> onselect
> onchange

Well yea. But this would be something we could/should add to a totally
reformulated "FORM_v2" cObject.

> title

This is already being handled by "titleText".

> style

Using id's and classes is already enough to style those widgets.

Cheers,
Ernesto