Changing tabs doesn't always show correct node name

[lovelaced]

It seems like when switching between tabs, sometimes - mostly when the number of nodes on the networks is the same (i've seen this with 6) - the nodes will appear with the names from the previously selected tab.

[dvdplm]

Chrome or FF? Not seeing this on FF nightly or Chrome Canary macOS. :/

[lovelaced]

Firefox 86.0.1

[chevdor]

What I see (testing with a single node with the same name on westend/kusama/polkadot) is that there is a slight delay before the nodes list updates when you swith tabs.

The header updates immediately but I can indeed see that the list of nodes and their stats hang a little bit (around 1 second).
To be honnest, I am not really surprised with the behavior. This is likely due to the content of a tab but being always cached and the update comes whenever the backend pushes new data.

Context:

• kubernetes:
  • 1 kusama node
  • 1 polkadot node
  • 1 westend node
  • 1 telemetry backend
  • 1 telemetry frontend
• brave browser Version 1.26.77 Chromium: 91.0.4472.164 (Official Build) (x86_64)

Everything running in a local cluster (so no external routing delay, no cloudflare, etc...).

[chevdor]

I tried a GIF but it does not really render the issue as it skipps frames. the following is what I see. You can observe the number of peers when switching tabs.

tag_lag.mov

@lovelaced does it look like what you are/were observing ?

[jsdw]

I saw this as well in various local tests (I happened to have 4 nodes total; 2 p[er chain). The node names always updated for me eventually, but there was sometimes a delay of maybe half a second to a second before they did, as if they only updated when some other node update came in perhaps.