Working here in Firefox, Chrome, and Edge on Windows 10 64bit desktop system and with Safari on iPhone in iOS system. With desktop, right click to open the mysteries of "inspect element" reveals the header has some properties inherited from "table" along with extensive specification of fonts, drop-downs, links, and the like. Since the blue bar is baked into the HTML code of the site, you might want to experiment with other browsers, close and reopen browser, repeat after full shut down and restart of system. After that, glitch resolution likely goes beyond my abilities.
PC machine? If so try F11 key. That will toggle that bar showing/not showing. I've noticed it sometimes gets turned off (Blue bar not showing) after a very tall DPC image. My 2 cents... Good luck
Edited: Oops I've just realized that what I wrote above applies to the blue bar showing different tabs and the search bar, not to the top line of DPC.
Very strange. Windows Edge (IE) it works fine. Chrome it still isn't working (no nav links), and I even just updated to the newest version - still no luck. Guess I'll have to use the Edge browser for a bit.
When I log out and visit DPChallenge as a visitor the links are visible. When I log back in they go away. Only using Chrome am I getting this behavior.
Chrome it still isn't working (no nav links), and I even just updated to the newest version ...
Well, that's probably the problem -- personally I try to never "update" anything unless it isn't working anymore ...
I think there was a recent overall site update to make the pages secure (i.e. "https://...") -- try checking your Chrome prefs to see if you need to change some setting ...
Chrome it still isn't working (no nav links), and I even just updated to the newest version ...
Well, that's probably the problem -- personally I try to never "update" anything unless it isn't working anymore ...
I think there was a recent overall site update to make the pages secure (i.e. "https://...") -- try checking your Chrome prefs to see if you need to change some setting ...
Well, it wasn't working BEFORE I updated Chrome either. I just went ahead and updated to see if that fixed it. I'll dig into settings tomorrow. Good advice - thanks! :-)
