"More" link in top navigation can't be accessed without JS

[alphagov]

"More" link in top navigation can't be accessed without JS

[thomasleese]

Has also happened in https://govuk.zendesk.com/agent/tickets/2446037

[fofr]

@h-lame Did Whitehall admin disable SRI attributes in the end?

[fofr]

"More" should probably link to a page that shows those navigation options. Then JS can prevent that link from triggering and show the dropdown for users with working JS.

[gpeng]

The ticket to fix this this is on our doing board. https://trello.com/c/2wYn3eJi/202-new-document-tab-does-not-display-dropdown (well, it's actually the new document tab but it's the same problem). Would be good to discuss/pair @fofr.

[h-lame]

@fofr I haven't removed SRI from the admin template, and it doesn't look like anyone else has either.

If it's causing lots of problems because of publishers working on networks that are monkeying around with the assets then removing SRI (even though it's doing its job properly!) seems like a pragmatic workaround for the problem. It'd be good to couple that with a spike/reivew to work out the scale of the problem as I suspect it's not just the more tab or new document tab. I wouldn't be surprised if large parts of whitehall admin were not progressively enhanced at all, so fixing just the bits that have been reported won't be enough. Once we've completed that review and fixed any problems we find we should be safe to re-introduce SRI safe in the knowledge that any monkeying about with the assets will be blocked, but also the publishers will still be able to get their work done.

[fofr]

@h-lame Completely agree. Suggested to @gpeng that we audit Whitehall for JS only features.

[gpeng]

On the backlog 👍 https://trello.com/c/Ly0hzsOT/1098-some-functionality-in-whitehall-admin-doesnt-work-at-all-without-javascript