Closed andysellick closed 3 years ago
Just to make sure that this isn't missed, this concerns the navigation header component.
We found that this has been fixed in https://github.com/alphagov/govuk_publishing_components/pull/2388.
Separately, I'm going to see if there could be further improvements to the way this component loads and initialises.
Spotted this while developing locally with
government-frontend
. I'd broken the scroll tracking JavaScript and when the page rendered it looked like this:This was in development and hopefully we'd catch any obvious JS errors like this before going to production, but it's always possible that a JS error like this could occur for another reason (we get loads of JS errors in LUX which seem to be due to things like conflicts with browser extensions, or if someone's connection dies mid-download, for example).
(apologies for the nebulous 'this might break bye' issue, but I thought it would be worth recording edge cases like this)