search

rjanicek / vice.js

Versatile Commodore Emulator for JavaScript
152 stars 25 forks source link

Broken in Chrome 39+ #3

Closed ociebieda closed 9 years ago

ociebieda commented 10 years ago

Hello. I tried your online demo and it seems that this emulator does not work with Chrome at all. I tried Prince Of Persia and Monster Busters. I can see title logo in first game, and hear short intro sound in second game. After this, emulator dont do anything and seems to be frozen. Everything is working correctly on FireFox. I am not sure what is going on, but I dont think you should blame Chrome. I played more than 20 JavaScript emulators last week for different old computers and consoles, and none of them had problems to work under Chrome (in fact they worked faster than on FireFox).

rjanicek commented 10 years ago

Tested in Chrome 38.0.2125.104 m on Windows 8.1 and both games work. Can you provide more information on your environment please?

ociebieda commented 10 years ago

Chrome 39.0.2171.13 beta-m (64-bit), Windows 7 64-bit. It is possible that they made changes in Chrome 39, coz they do this all the time.

rjanicek commented 10 years ago

Was able to reproduce on Chrome 40.0.2189.0 canary (64-bit). Will monitor and if still an issue when Chrome 39 reaches stable channel, will fix at that point. Thank you for the heads up.

On Tue, Oct 14, 2014 at 6:50 PM, ociebieda notifications@github.com wrote:

Chrome 39.0.2171.13 beta-m (64-bit), Windows 7 64-bit. It is possible that they made changes in Chrome 39, coz they do this all the time.

— Reply to this email directly or view it on GitHub https://github.com/rjanicek/vice.js/issues/3#issuecomment-59130496.

rjanicek commented 9 years ago

Chrome 39 is now on stable branch and seems like the issue has been resolved.

ociebieda commented 9 years ago

Well, it seems like Chrome is starting to have many bugs with each update. I dont know what they are doing, but I found this browser very problematic with many JS and HTML projects, like it was not before for me. They also started to drop support for some functions, like they introduced pixel art methods in two releases ago, and now they decided they will not support it. They also changed audio engine some time ago. The only thing that makes me stay with them yet, is that they still have fatest website rendering. I hope that they will stop this madness and back to stability like it was in the past, and will not remove functions so it will keep them compatible backward, not forcing coders to change their work again and again.