UI Bug "expand" FreeNAS 11.3U3.2

[websmith]

Hi,

It seems like there is a bug in the UI - but not consistent.

I have two servers, both running FreeNAS 11.3U3.2
FreeBSD 11.3-RELEASE-p9 (FreeNAS.amd64) #0 r325575+588899735f7(HEAD): Mon Jun 1 15:04:31 EDT 2020

Whenever I try to use the "expand" arrow to the right on one of the servers - it expands, but it expands below in Z-index to the area below it, i.e. the area with 1-1 of 1 - but only one of my servers - the other it does not happen on.

When it expands it looks like this:

It took me a while to figure out that I could scroll in the area above and see the edit buttons etc.

in the javascript console I get this error:

Code:

main.b1a880dce810e0926195.js:1 ERROR Error: Element is not detectable by this strategy.
    at Object.addListener (scripts.22cb7218f2daa92927e9.js:1)
    at scripts.22cb7218f2daa92927e9.js:1
    at scripts.22cb7218f2daa92927e9.js:1
    at t (scripts.22cb7218f2daa92927e9.js:1)
    at HTMLObjectElement.o.onload [as __zone_symbol__ON_PROPERTYload] (scripts.22cb7218f2daa92927e9.js:1)
    at HTMLObjectElement.T (polyfills.0d316611ee439c4773ba.js:1)
    at e.invokeTask (polyfills.0d316611ee439c4773ba.js:1)
    at Object.onInvokeTask (main.b1a880dce810e0926195.js:1)
    at e.invokeTask (polyfills.0d316611ee439c4773ba.js:1)
    at t.runTask (polyfills.0d316611ee439c4773ba.js:1)

On the server where it works, I don't get this error, so I expect the javascript error is the culprit.

The browser I am using is the "new" edge browser in windows 10: Version 83.0.478.56 (Official build) (64-bit) - the version based on chromium
This issue does not happen when I use Chrome Version 83.0.4103.116 (Official Build) (64-bit)

Initially I thought it was a browser issue, but since its not consistent on the two servers running the same version of FreeNAS I think it must be an issue in FreeNAS itself.

Has anyone experienced the same and have any good ideas on how to resolve it?

And don't say use Chrome

 

[sretalla]

Have you entirely cleared the browser cache on Edge Chromium for your FreeNAS servers?

 

[websmith]

Have you entirely cleared the browser cache on Edge Chromium for your FreeNAS servers?

CTRL+F5 usually does the trick when other "services" updates UI - and clearing the cache makes no difference - and to be honest it should really not be necessary to clear the cache - http meta tags is created for this purpose so server can signal that content is stale, or ETag etc. you name it. Plenty of ways to get around people not having to manually clear a cache.

 

[jimmyhiggs337]

CTRL+F5 usually does the trick when other "services" updates UI - and clearing the cache makes no difference - and to be honest it should really not be necessary to clear the cache - http meta tags is created for this purpose so server can signal that content is stale, or ETag etc. you name it. Plenty of ways to get around people not having to manually clear a cache.

not sure if you're still having this issue, but after clearing the cache I was still having this issue, what fixed it for me was going into my extensions and clearing out some that modify or monitor code in the browser