[TYPO3-core] RFC: #3527: Bug: Wrongly encoded characters in mail form validation popup

[Francois Suter]

Hi,

> Yes, but ONLY if tslib_content does something like that:#
> 
> $content = <<<EOT
> <script>
> var dummy = '$foobar';
> </script>
> EOT;
> 
> Ie. it creates a JS string embedded in the HTML code. In this case the
> browser should handle the charset all by itself.

That's the case. The "onSubmit" call is prepared by tslib_content and 
added to the HTML of the FORM.

> Really old browser that require unescape() to handle latin1 will choke
> on utf8 no matter what you do :)

Yes, but I think it's reasonable to forget about those.

So here's new patch removing calls to rawurlencode() in tslib_content 
and all calls to unescape() in the validateForm JS.

Hoping I'm on the right track this time.

Cheers

-- 

Francois Suter
Cobweb Development Sarl - http://www.cobweb.ch
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: bug3527-v2.patch
Url: http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20090327/4d190be3/attachment.txt