
Clicking any tabs ends up in the sidebar doing this:


I've now installed the 'release' version of Firefox, which calls itself 68.0.2 and I have the same issue there and the version of FF Developer Edition I have is 69.0b13 and I have the same issue still.agw wrote: ↑Wed Aug 14, 2019 12:20 amThe developer edition is not the latest version of Firefox. It's a beta build and in Mozilla's own words it is "an unstable testing and development platform".
When I test the page using the latest release beta 69.0b13 (64-bit) the options menu and aircraft list are displayed normally.
Code: Select all
Version: 3.0.0 Beta
12/06/2019 19:06:05
Environment: Mono 64-bit
I do have some custom content but disabled it throughout testing and the issue persisted (cleared cache on the browser too once disabling the content) - So it's not that.
Possible? But I tried a portable version of firefox (without FF Sync enabled) and this has persisted over an entire PC re-install.agw wrote: ↑Fri Aug 16, 2019 12:32 amb) Your Firefox installation is knackered. Try getting rid of it entirely, reboot to make sure no lingering vestiges remain and then reinstall maybe? Are you installing using the distribution's package manager or using bundles you're downloading off a site? Maybe go for the package manager version if you aren't already?
If I use MS Edge or Chrome on the same PC the issue does not appear.agw wrote: ↑Fri Aug 16, 2019 12:32 amIf you have other machines on the network, e.g. a tablet, then you could try fetching the desktop page over the network and seeing if it works OK from there. The LAN address of the desktop page can be shown on the server's main screen, adjust the dropdowns under the list of clients.
I had not tried this, but there is one error when you open the options UI, and a second error once it's been closed for a few seconds.agw wrote: ↑Fri Aug 16, 2019 12:32 amHave you tried pressing F12 to get the console window up and seeing if there's any messages in the console window? You might get warnings about a missing .TS and .MAP file, you can ignore those, likewise if you're using Google Maps then it might say that it's fetching a later version of the map than the one requested. But you should not get any errors, if you see any then let me know what they say (and definitely disable the custom content plugin to see if they go away).
Code: Select all
TypeError: b is null desktop-0-bundle.js line 60 > eval:224:1838
useSvgGraphics [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:224
useEmbeddedSvg [redacted]/VirtualRadar/desktop-0-bundle.js:189
createIcon [redacted]/VirtualRadar/desktop-0-bundle.js:189
refreshAircraftMarker [redacted]/VirtualRadar/desktop-0-bundle.js:189
refreshSelectedAircraft [redacted]/VirtualRadar/desktop-0-bundle.js:189
raise [redacted]/VirtualRadar/desktop-0-bundle.js:127
setSelectedAircraft [redacted]/VirtualRadar/desktop-0-bundle.js:174
f [redacted]/VirtualRadar/desktop-0-bundle.js:171
aircraftListUpdated [redacted]/VirtualRadar/desktop-0-bundle.js:171
raise [redacted]/VirtualRadar/desktop-0-bundle.js:127
applyJson [redacted]/VirtualRadar/desktop-0-bundle.js:174
fetchSuccess [redacted]/VirtualRadar/desktop-0-bundle.js:177
d [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:60
l [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:60
fireWith [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:60
q [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:60
d [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:60
TypeError: b is undefined desktop-0-bundle.js line 60 > eval:251:8960
intersects [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:251
_clipPoints [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:251
_update [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:251
_reset [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:251
onAdd [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:251
_layerAdd [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:251
whenReady [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:251
addLayer [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:251
addTo [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:251
addPolyline [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:262
a.widget/</j[b]</< [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:82
createTrail [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:189
updateTrail [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:189
refreshAircraftMarker [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:189
refreshMarkers [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:189
foreachAircraft [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:174
refreshMarkers [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:189
refreshMarkersOnListUpdate [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:189
raise [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:127
applyJson [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:174
fetchSuccess [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:177
d [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:60
l [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:60
fireWith [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:60
q [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:60
d [redacted]/VirtualRadar/desktop-0-bundle.js line 60 > eval:60
Clearing settings (including initial settings set) resulted in no difference.agw wrote: ↑Fri Aug 16, 2019 12:32 amMaybe the splitters have gone a bit weird? You could try resetting the site's settings - go to the settings page off the server main screen (see the dropdowns below the connected clients list) and on there choose export settings, keep a copy of the text that appears just in case you want to put the settings back, and then click the button to remove all settings. Then go back to the main site, reload and see if that cures it.