UIKit Nav Cleanup

[sghoweri]

Long overdue front-end cleanup of the Nav component to be more maintainable, more easily updated in the future and more performant. Not 100% where I want to be with this ideally (maybe 80%+) but definitely puts us in a much better spot than before.

At a high level, this includes one new feature, but most of this is just under the hood refactoring.

New Feature (Fix?)

• Only allow one top level nav link open at a time while on larger screens / nav displays as a dropdown menu

Refactor

• Updates us from using Preact v8 to Preact v10 so we can fully take advantage of Fragments, etc
• Breaks the Nav up into smaller, more manageable sub-components
• Significantly reduces the amount of UI logic required (especially with handling the active Nav item)
• Simplifies the CSS to deduplicate and streamline everything; sets us up for eventually allowing end users to officially be able to customize the UI via CSS Custom Properties

I still need to finish up doing cross browser testing on this but early testing seems very promising.

Side Note: I mistakenly branched this off of #1034 so I'd recommend we merge that down first to avoid merge conflicts + reduce any potential rework!

[coveralls]

Coverage remained the same at 76.959% when pulling a2e22ee on feature/uikit-nav-refactor into a5a1265 on dev.

[bmuenzenmeyer]

@sghoweri are you using this to make progress against #1103 or can it be independently merged?

[sghoweri]

Independent — actually started this before #1103!

[sghoweri]

Update: there's at least two small CSS fixes that'll be needed here before this is good to go in IE 11 + Firefox, FYI!

[stale]

It's hard to keep track of everything. This issue has been automatically marked as stale because it has not had recent activity, neither from the team nor the community. It will be closed if no further activity occurs. Please consider adding additional info, volunteering to contribute a fix for this issue, or making a further case that this is important to you, the team, and the project as a whole. Thanks!

[bmuenzenmeyer]

@sghoweri just checking in on this - I havent reviewed in quite a while, citing your above comment

[JosefBredereck]

Update: there's at least two small CSS fixes that'll be needed here before this is good to go in IE 11 + Firefox, FYI!

Do you need a review for this topic or is it not finished at the moment?

[stale]

It's hard to keep track of everything. This issue has been automatically marked as stale because it has not had recent activity, neither from the team nor the community. It will be closed if no further activity occurs. Please consider adding additional info, volunteering to contribute a fix for this issue, or making a further case that this is important to you, the team, and the project as a whole. Thanks!

[stale]

It's hard to keep track of everything. This issue has been automatically marked as stale because it has not had recent activity, neither from the team nor the community. It will be closed if no further activity occurs. Please consider adding additional info, volunteering to contribute a fix for this issue, or making a further case that this is important to you, the team, and the project as a whole. Thanks!