is this gonna be implemented in 1.3? i don't like adding that kind of code
to my dependency list.
I've created a class that does pretty much that (exactly the same methods).
i see that the code writer also had the same problem -
if(typeof window.onhashchange == 'function' && fn !==
window.onhashchange) {
//bind the method to the mootools method stack
window.addEvent('hashchange',window.onhashchange);
//remove the event
window.onhashchange = null;
}
and then they rewrite the event.
is that onAdd - onDelete the way to add events to mootools?
On Tue, Jun 15, 2010 at 7:12 PM, Ryan Florence <[email protected]> wrote:
> http://github.com/matsko/Mootools-window.onhashchange
>
> This works awesome if you need cross-browser support.
>
> On Jun 15, 2010, at 9:50 AM, אריה גלזר wrote:
>
> no good...
> btw - FF is doing fine with addEvent. haven't tested on ie8 yet though.
>
> On Tue, Jun 15, 2010 at 3:28 PM, Oskar Krawczyk
> <[email protected]>wrote:
>
>> Try doing:
>>
>> $extend(Element.NativeEvents, {
>> onhashchange: 1
>> });
>>
>> Before adding the event.
>>
>>
>> On 15 Jun 2010, at 12:59, אריה גלזר wrote:
>>
>> hey
>> for some unknown reason, doing
>> window.addEvent('onhashchange',function(){...})
>> doesn't work for me on chrome 5, only
>> window.onhashchange = ...
>>
>> anyone knows why? this is obviously a problem, since it means i have to
>> trust the user not to overwrite my event
>>
>> --
>> Arieh Glazer
>> אריה גלזר
>> 052-5348-561
>> 5561
>>
>>
>>
>
>
> --
> Arieh Glazer
> אריה גלזר
> 052-5348-561
> 5561
>
>
>
--
Arieh Glazer
אריה גלזר
052-5348-561
5561
