Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Recommended browser for roll20?

Hi I currently have more and more problems with chrome using roll20 (first the spdy errors and NOW bad requests the later dont go away until I clear the cache and happen every 5th click -.-). I know with IE some roll macros don't work. So is there any recommended browser for using roll20?
The current, non-test versions of Google Chrome and Firefox are the only officially-supported browsers of Roll20.
Silvyre said: The current, non-test versions of Google Chrome and Firefox are the only officially-supported browsers of Roll20. I'm using the google chrome and.........have SEVERE troubles. First time and again a  "spdy error" thus errors for a protocl that google wanted to discard for years by now and still didn't  which only go away after 30-90 minutes and then since today suddenly "400 bad request" errors from the cloud. :/
I find Firefox more stable - that and using Skype for voice (no video) has cleared up some issues for me (GM). The only real problems we have now are related to sheet we're using.
There is an interesting article involving the ERR_SPDY_PROTOCOL_ERROR messages that I found recently: <a href="http://techdows.com/2015/08/fix-chromes-err_spdy_p" rel="nofollow">http://techdows.com/2015/08/fix-chromes-err_spdy_p</a>... The thing that interests me the most is that it could be related to Avast's Web Shield. &nbsp;I have recently added exclusions for the Roll20 addresses, hopefully this will prevent the problem, because it is very frustrating when this happens. &nbsp;Essentially you need to stop all Chrome processes (including googledrivesync (if present)) and restart them, sometimes this doesn't even work.
yepp there are even other workarounds like deactivating the protocoll but they dont work with the current chrome versions sadly (and funny part is still google said "the protocol is no longer used nor supported by us" and google is the only one looking for it and not finding it......causes the problem......drop