Page 1 of 1

Google Chrome

PostPosted: Wed Apr 28, 2010 3:32 am
by nagerous
For some reason I am having trouble running scripts on Google Chrome.

Clickable Maps is the only script I have tried that has run without problems. BOB hasn't appeared at all, meanwhile Map Rank and Tour Stats appear on the outside to work but as soon as you input any data then do a search a popup appears but it is blank.

Any help/advice would be appreciated.

Re: Google Chrome

PostPosted: Wed Apr 28, 2010 3:43 am
by Dako
Most of the tools are Chrome incompatible. Main problem is - Chrome doesn't have correct implementation of save/load function. So you cannot store snapshots and load preferences.

Unless you can nag Script dev's to upgrade their script - there is no way you will get them running :-(.

Re: Google Chrome

PostPosted: Wed Apr 28, 2010 3:45 am
by nagerous
Dako wrote:Most of the tools are Chrome incompatible. Main problem is - Chrome doesn't have correct implementation of save/load function. So you cannot store snapshots and load preferences.

Unless you can nag Script dev's to upgrade their script - there is no way you will get them running :-(.


Thanks for the quick answer. For some reason firefox chooses to crash on me every time I load it up on this computer even after reinstalling, so guess I'm just stuck with CM for now!

Re: Google Chrome

PostPosted: Wed Apr 28, 2010 4:09 am
by sherkaner
Dako wrote:Most of the tools are Chrome incompatible. Main problem is - Chrome doesn't have correct implementation of save/load function. So you cannot store snapshots and load preferences.

Unless you can nag Script dev's to upgrade their script - there is no way you will get them running :-(.

Yep, he's right. I used some code to replace the mentioned functions for CM, that should work for most other scripts too (Actually, it was a bit more work. But most scripts are simpler, hopefully they don't need that).

Exception is BOB.. I'm trying to create a version that works with Chrome now, but there are some solutions in that code that just won't work with Chrome. But I hope I can create a workaround (which could be slower btw.) when chrome is used.