[TYPO3-core] RFC: fix bugs #3655 and #4701 - no wrappers for certain events

Michael Stucki michael at typo3.org
Sun Feb 4 17:47:18 CET 2007


Hi Martin,

I quickly talked to Oliver, apparently there was a small misunderstanding:
The existing handlers still worked like before, but the new ones failed
partly. However, this time even this worked on his IE7 installation
(correct, Olly?)

Conclusion: +1 for the optimization (it doesn't change any behaviour), +1
for extending the array.

However, we are aware that some of the new events might not work on some
browsers (which is not a TYPO3 specific issue, however)...

- michael

Martin Kutschker wrote:

> Oliver Hader schrieb:
>> Hi Masi,
>> 
>> Martin Kutschker wrote:
>>> But after writing I was wondering if the events are applied correctly
>>> (window vs. document vs document.body). Plus there is the issue of the
>>> old codes questionable behaviour of setting both an onload-attribute
>>> and an event property.
>>>
>>> What do you think?
>>>
>>> Masi
>> 
>> First of all: Good idea! ;-)
>> 
>> I tested the functionality in frontend with onload and onkeydown events.
>> Firefox2 works like a charm, IE7 doesn't!
> 
> Interesting as there was no change in the JS code for onload at all! An
> according to the docs on MSDN onkeydown is a property of the document
> object. onload used to work for document, but is accordiing to both IE
> and Firefox docs really a property of the window object.
> 
> Masi

-- 
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/


More information about the TYPO3-team-core mailing list