Senior Member
Join Date: May 2017
Posts: 135
|
Quote:
Quote:
For this one, could you send us a bug report with some screenshots and the specific Firefox version number(s) you're using? |
||
#11 |
Senior Member
Join Date: Mar 2016
Posts: 453
|
|
#12 |
Senior Member
Join Date: Jul 2008
Posts: 1,321
|
I'm using Firefox ESR because I use several extensions that don't have adequate replacements in Quantum. I'm hoping that by the time ESR switches the extension authors will have better choices available.
Currently Running: Pathfinder Second Edition Currently Playing: Pathfinder First Edition, Star Trek Adventures Former HL Games: D&D 4e & 5e, Mutants & Masterminds 2E & 3E, Savage Worlds |
#13 |
Member
Join Date: Jun 2012
Posts: 59
|
As far as offline use goes, I managed to use HLO at a convention last weekend without a connection. To a degree, it worked.
I began by prepping when I did have a connection, opening a new browser tab for every page of HLO that I would need. Then during game I would just switch to the appropriate tab. Clicking things to get details on them generally still worked. I didn't try to change anything, so I don't know if that would work or not. |
#14 |
Member
Join Date: Apr 2016
Posts: 30
|
Here's a good example of a stable wired connection to HLO:
EDIT: This issue was repeatable for me each time I logged in to HLO from Chrome. The workaround for me is to close Chrome and relaunch HLO, then the connection doesn't flap for the remainder of that session. If I close out and connect again later, I have to repeat the double-launch process. Last edited by DreadKatak; February 26th, 2018 at 01:18 PM. Reason: Additional comment |
#15 |
Senior Member
Lone Wolf Staff
Join Date: Apr 2013
Posts: 691
|
Quote:
Usually, all I need to do is refresh the browser window (F5 or command+r depending on your platform) to kick it back into a normal state, I think. I don't think you should need to completely close and reopen the browser. |
|
#16 |
Member
Join Date: Apr 2016
Posts: 30
|
Quote:
ie, it automatically is logged in when I first launch the site in browser. That may be contributing to the problem? I also get the following messages, which may also help (looks like it may try to connect too fast or something?): Last edited by DreadKatak; February 27th, 2018 at 05:30 PM. |
|
#17 |
|
|