Closed Designer-Drums closed 5 years ago
Yep. Same issue as #5. I'm also seeing the same thing with the Android FF version, but the desktop FF version seems to be working fine. In all cases, I tested using the latest version, 1.12.1
Thanks both for the report. I'll dig into this tonight..
I had forgotten last night that I was releasing an older version for Chrome due to this bug (I really should have tagged/branched that..)
I've made a change which I hope should fix this.
I believe it was related to using browser
instead of chrome
in the chrome version. Firefox can handle either, but chrome is picky. I've added that to the platform specific file so I can get the right variable for the browser which is being used
Chrome is now working properly. Still seeing the same behavior on Android FF though - should I open a separate issue for that?
I think that the most recent 2 commits should fix the Android issue. I've published it to the mozilla store as 1.12.3 (and releases page).
Hooray, it's fixed! Thanks again for all your great work on this.
Woo! Thanks for always testing it so quickly!
Looks like this issue has reappeared. Please fix. :) Thanks!