nemac / seldon

openlayers webgis
4 stars 3 forks source link

Broken ForWarn II Comparisons Theme #94

Closed popensesame closed 3 years ago

popensesame commented 3 years ago

URLs from Joe S:

https://fcav2.nemac.org?theme=ForWarn2_Compare&layers=FW_20180609_ALC_LEGACY,AAB,AAC&mask=Forest&alphas=1,1,1&accgp=G16&basemap=None&extent=-9246789.4017348,4601416.6612726,-8855431.8169146,4786394.2697228

https://fcav2.nemac.org?theme=ForWarn2_Compare&layers=FW_20180609_ALC_LEGACY,AAB,AAC&mask=Forest&alphas=1,1,1&accgp=G16&basemap=None&extent=-9248241.7052852,4621213.8516116,-9052562.9128754,4713702.6558366

https://fcav2.nemac.org?theme=CONUS_Vegetation_Monitoring_Tools&layers=FW_20180524_MEDIAN_ALL_YR_FW2,FW_20180601_MEDIAN_ALL_YR_FW2,FW_20180609_MEDIAN_ALL_YR_FW2,AAB,AAC&mask=Forest&alphas=1,1,1,1,1&accgp=G04&basemap=None&extent=-9246789.4017348,4601416.6612726,-8855431.8169146,4786394.2697228

From Steve N:

I can see the maps from your links, but the TOC fails to open on your share URL so I can see what layers you have open or to explore the products. What’s up with this new problem now?

Steve N:

I’ve got it to work on a different browser by cutting and pasting. Sadly, IE-FS version remains our agency default browser, and we were all just upgraded us to Win 10 so we need to all adjust our defaults and or just remember to avoid this by always using FF or Chrome, even with a share URL.

We’ve had substantial issues with FCAV in IE over the years, and this new issue could cause major headaches for our FS clients in particular, but as problems seem to be a recurrent shortcoming of the RIP IE browser, we need to ask if it’s worth effort to address. I’d be happy with a pop up with sirens and flashing red strobe lights to warn all IE users to use a different browser, as there are likely other issues that will crop up, just as we’ve seen time and time again with IE.

What I got was a Map Layers menu that didn’t let me close any higher level group name by clicking on it. I could click on a different header to close the Boundaries default though, however, this didn’t help, as under the header ForWarn II Comparisons, it was all white without any content at all, as if it choked up while rendering, but with no error messages. Oddly, the other headers showed their content correctly.