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

More issues with Chrome that Firefox doesn't have

Hey guys, I'll jump straight to the point: Chrome occasionally stops working for roll20 in the editor. From what I can see this only happens on my macbook, while on my windows desktop it doesn't happen. Basically, after some time in the editor, you'll notice that clicking on tokens no longer shows the blue outline of that token, and moving it around, rotating it, all that stuff, doesn't affect it. In truth it actually does move it, but the map simply doesn't display it; viewing the map on another computer shows the changes. This makes it impossible for me to know where tokens are except by hovering the mouse above squares until it I find it. Firefox works fine. This happened many months ago and stopped doing it, then all of a sudden started doing it again recently.
Hi Laurence, Could you answer some of the questions below in regards to this issue? Specifically browser version and extensions, as well as the console log of when this behavior occurs would be most useful! :) Description of setup Browser + Version Browser Addons/Extensions Operating System Bug Triage Results Please carefully work through to the first three steps of our guide to Solving Technical Issues : Step 1: Make sure to use the right browser Please check if these issues persist when using both Chrome and Firefox. Step 2: Ensure that there are no extensions/addons interfering with Roll20 Please disable all add-ons/extensions and anti-virus programs. Step 3: Clear your cache If none of the above succeed in resolving the problem, please thoroughly work through Step 4 . (Don't forget the complete Console Log!) Supplemental Information Including screenshots by using the "Attach a File" link when submitting a post can provide a great deal of information! The more information you can provide, the better able a fix will be reached.
Another thing that could help is an approximate time frame for this event, for example, if it only happens after 5 min, after 15 min, after 30 min, after 1 hour, I'm specifically assuming that this might be some form of built-in timeout for the Browser, such as "after 1 hour, stop updating JavaScript", this might end up getting tracked in the Console Log when it first triggers, so try to get the time frame narrowed down if you can to help the Devs.