The pages are made up of many individual components that are retrieved from the server - if your browser thinks that one or more of them is up to date, it won’t fetch it, so you can end up with components from different revisions being used by your browser with consequent issues.
The first thing to try is a force reload the console page - it’s like a more aggressive version of refresh/reload - depending on browser / OS you use shift or option or ctrl or alt - most browsers show a change of name in the menu when you have the modifier key held down so you know it’s going to do it.
This is not the well worn trope of clearing your cache which will remove everything, but an occasional tidy up doesn’t hurt if you are on a fast connection, not so great if you are out & about on slower mobile internet.
The acid test is to load up a different browser that has no cache and try that. For instance, I use Safari for general use, Chrome for sys-admin - websitery, TTS console(s), etc etc and keep FireFox in reserve for clean “no-cache” testing.
The login flow from https://thethingsnetwork.org has recently changed but I’ve just logged in OK, I know that’s an irritating “works for me” phrase, but I have sanity checked it.