Do Not Support CMS Menu Dropdown Nav Link

[wesleyboar]

Status

Moved to FP-1235.

Archived

Original description...

Status

1. [Intended to] be done via Header Redesign → FP-1458 #101[, but that ticket is taking too long.]
2. Performed via b2cec49 (but not in isolation, see taccsite_cms/templates/cms_menu.html).

Goal

Remove support for a nav menu item to be a link and have a dropdown.

Requirements

1. CMS navigation must not support top-level link click and dropdown simultaneously.
   1. This must be true for CMS pages.*
   2. This must be true for Portal pages (like Public Data).*
   3. This must be true for User Guide site (like [Frontera User Guide]).*†

* [This clarification was added] on 2021-08-11 during CEPv2 Testing Session.
† No CEPv2 website yet has dropdown menu and User Guide, so this requires special testing.

Background

This is a feature that @tacc-wbomar added that now needs to be removed.

Direction

To remove ad hoc per site…

Warning: This is not a long-term solution.
Caveat: This fix does not work on Portal pages, like Public Data.

The long-term solution is that the template markup should not create a link (because Design does forbids a page that both is a parent of pages and has its own content).

Add this snippet to the footer:

NAME: GH-129: CSS: Temp. Fix to Remove Dropdown Nav Link Support
HTML:

<style type="text/css">
/* Prevent user from functional hover and click on dropdown nav link */
/* TODO: After merge and deploy of GH-101 to this site, delete this snippet */
/* FAQ: GH-101 Solves GH-129 "the right way") */
.s-cms-nav .nav-item.dropdown .nav-link a:not(.dropdown-toggle):not(.dropdown-item) {
    pointer-events: none;
}
</style>

SLUG: gh-129-css-temp-fix-to-remove-dropdown-nav-link-support

[wesleyboar]

Migrated to FP-1235.