TYPO3 Core

- includes also the pass of metaCharset cause I don't want to instance an tslib_fe object (Opera needs the meta Content-Type tag to choose the correct charset / FF needs the Content-Type http header only)

here is the TS for using this new feature:

tt_content.image.20.1.imageLinkWrap.title = TEXT
tt_content.image.20.1.imageLinkWrap.title {
field = titleText
split {
token.char = 10
token.if.isTrue = 1
returnKey.data = register : IMAGE_NUM_CURRENT
}
}

tt_content.image.20.1.imageLinkWrap.alt = TEXT
tt_content.image.20.1.imageLinkWrap.alt {
field = altText
ifEmpty.field = titleText
split {
token.char = 10
token.if.isTrue = 1
returnKey.data = register : IMAGE_NUM_CURRENT
}
}

Just a small note so far: We cannot change the links for the popup windows because this would break compatibility with other extensions that use it.

NAK, if extension uses imageLinkWrap.
ACK, if the extension build its own link to showpic .

We can support backwards compatibility by checking the hash also the old way.

It is not so long since the handling with showpic was changed completely and this is a nice addon for supporting accessibility.

What's the point of the alt attribute in this context? The title of the original link should have made it clear that a blind user gains nothing by clicking the link.

Anyway, I think we could use a modified patch. As setting the alt and the charset will not allows any DoS attack it can be omitted from the md5-hash.

And I think the shorter name "charset" is fine for passing on the charset. The distinction between metaCharset and renderCharset makes no sense in this context.

Closing is okay for me :-)