Mobx/Digital twin UI issues on small screen - Tools menu

[zoran995]

When a user resizes the browser window there are a few edge cases that he can see

• related maps get moved to the second row when the user is logged, and there are three rows (first image), in my case between 768px and 797px (on longer names it will happen even earlier)
• before switching to mobile view there is a possibility to see something like on the second image (blue line around logo)
• on a screen with a width less than 1000px related buttons get out the window (user can't see the close button)
  
  
  

[zoran995]

Iphone X in landscape mode provides few edge cases for phones. Buttons help and feedback go out of the screen. Also, scale graph overlaps with a disclaimer, lat/lon info shows on the map although they don't have any function. Related maps close button goes out of the screen.

[zoran995]

Also, help UI is not responsive on screen size change so it doesn't get a scroll bar on smaller screens. The same thing is happening with the help panel. The help menu doesn't work on a mobile phone.

Helpful hints in workbench get cut off on a smaller screen.

[AnaBelgun]

Another example of Mobile/small screen issues with top menu bar.
On v8 based DE Africa the top menu bar completely disappears; there is no menu visible

[soyarsauce]

@reginapramesti this one please 🙂

[soyarsauce]

@reginapramesti to highlight remaining edge case things

[reginapramesti]

Edge cases that still need addressing:

• Left menu bar overflows to a 2nd row when logged in and screen width is between 768px and 797px
• Related maps gets cut off on smaller widths, and close button isn't visible
• Some MapIconButton overflows on smaller heights, so help and give feedback is inaccessible

[zoran995]

@reginapramesti Any thoughts on the fixing the MapNavigation overflow? I am thinking about something similar to the vscode sidebar overflow (composite side bar) which will group items into 3 dots icon on overflow, it will require a rewrite of MapNavigation

[AnaBelgun]

we'll need to discuss with @philipgrimmett when he starts next week