NCEAS / metacatui

MetacatUI: A client-side web interface for DataONE data repositories
https://nceas.github.io/metacatui
Apache License 2.0
41 stars 26 forks source link

Re-do responsive navigation #1598

Open robyngit opened 3 years ago

robyngit commented 3 years ago

Describe the bug On a small screen, the user profile menu sometimes appears outside of the minimal nav element, and above the portal editor content

To Reproduce Steps to reproduce the behavior:

  1. On any device < 770px wide, open the portal builder in the default theme. The menu will be expanded.
  2. Use the X (close) button to collapse the menu
  3. Press the hamburger button to expand the menu, the menu will appear as it does in the screenshot below.

Expected behavior The menu items should not overlap with page content, and should appear within the menu container

Screenshots

Screen Shot 2020-11-03 at 11 40 01

Desktop (please complete the following information):

Smartphone (please complete the following information): The screenshot shows an example of the issue on a simulated Moto G4 device, but this issue happens on chrome desktop as well, when the browser is < 770px wide.

robyngit commented 3 years ago

While working on this issue, I realized that the menu has bugs on all of the themes, not just the default one. Here are the issues I found:

In the Arctic theme:

In the KNB theme:

In all themes:


I think that a number of these issues are related to trying to make Bootstrap's dropdown menu open and close on hover rather than on click (what it's designed for). I wonder if, rather than trying to fix each of these bugs, it might be easier to re-write the NavbarView and templates to no longer use Bootstrap dropdown element, like the DataONE theme. Thoughts?

robyngit commented 3 years ago

See also https://github.com/NCEAS/metacatui/issues/615

amoeba commented 3 years ago

Thanks for writing this up and including all the screenshots, @robyngit! While I know some of our main page elements might take substantial work to make responsive, but I think it's important that at least our header, footer, and any navigation elements display well across devices. Simplifying/consolidating the header/nav across themes sounds like a really good move forward.

laurenwalker commented 3 years ago

I see this is in the REview/QA column @robyngit - Is there a commit attached to this issue or is it in progress?

robyngit commented 3 years ago

There aren't any commits for this issue yet, I put it on hold and in the Review/QA column because I wanted to get feedback on the best way forward to fixing these problems. (Also because I only just realized that the QA in Review/QA probably stands for Quality Assurance and not Questions & Answers...) I think it would be quicker to re-structure the NavbarView and templates rather than to try and fix the individual problems. When working on this, I found that trying to fix a problem in one theme led to new problems in other themes. Any thoughts on this?