-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncaught TypeError: Object [object global] has no method 'attachEvent' #5
Comments
Seems like the |
How is that even possible, Mr. Holmes? |
For instance, if you call this method on a server instance (nodejs, iojs, nw, electron) which doesn't have a You didn't provide more details about your context, so I'm assuming some possibilities here. :) Makes sense? |
totally, was more of a joke. i'm investiganting |
Oh wait, the problem is the method So for using hash in a forced way, there must to be added some cross-browser capabilities to it, among tests of course. |
okie dokie. i went into this route because i'm having the classic "base_path" issue when using it inside of node-webkit. it does work allright when testing on OSX but on my virtual machine with a "mounted folder" it's getting confused. i'll have a better look soon. i tried using page.js from TJ which did not have this issue, but in the other hand for some reason doesn't trigger the routes when the pushState changes ( using node-webkit 0.8.6 ). i thought this was supposed to be easy :P |
In this case here, it seems simple. :) Basically one have to demystify a cross-browser way to do Cross-porting this code block should be enough: window.attachEvent('onhashchange', function(){
self.emit('url:change', self.pathname())
}, false); However, you've mentioned the |
yeah, will probably use a base_path hack |
thanks! |
By forcing the HASH api on ways-addressbar like this:
i'm getting an error:
Uncaught TypeError: Object [object global] has no method 'attachEvent'
on chrome.The text was updated successfully, but these errors were encountered: