hashchange binding with mootools broken #124

Closed
tracer99 opened this Issue Oct 23, 2012 · 2 comments

Comments

Projects
None yet
3 participants
@tracer99
Contributor

tracer99 commented Oct 23, 2012

canjs + Mootools means that routing doesn't work.
According to discussions with #mootools, it's because hashchange is not officially supported as a native event to bind to.
This one line apparently resolves this

Element.NativeEvents.hashchange = 2;

Mootools 1.5 has fixes to native events to handle this.

See http://jsfiddle.net/6J3G2/ for example of non-functioning routing.

@justinbmeyer

This comment has been minimized.

Show comment
Hide comment
@justinbmeyer

justinbmeyer Oct 30, 2012

Contributor

Thanks! We will fix this soon.

Contributor

justinbmeyer commented Oct 30, 2012

Thanks! We will fix this soon.

@imjoshdean

This comment has been minimized.

Show comment
Hide comment
@imjoshdean

imjoshdean Nov 5, 2012

Contributor

Added hashchange and popstate to the native events, and it looks like that did indeed fix it on Can 1.0.7.

This will be resolved in 1.1.

Contributor

imjoshdean commented Nov 5, 2012

Added hashchange and popstate to the native events, and it looks like that did indeed fix it on Can 1.0.7.

This will be resolved in 1.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment