Hi, noticed the redesign of the header, nice, but a little issue, on the user menu scrollbars appear when they shouldn’t (on a resolution:
This seems to be due to an overflow-y property applied to all menus in header:
If I deactivate this overflow-y, menu then shows properly:
This happens on a 4k screen with a body of 1562x2800
I think the menu needs to be a tad wider (and overflow-Z at least set to hidden), or get rid of the overflow-y altogether.
Good catch, I need to set that property to auto. It needs to be there in case someone has a shorter vertical resolution.
Not sure if it’s related, but I also noticed on chrome on my Samsung galaxy tab s9+ (vertically and horizontally) when I click on that drop down menu it won’t expand, it just goes to my profile.
It works fine on chrome on iOS though.
That issue, I’m not seeing but when I do click on the search text box from chrome on my android tablet, vertically and horizontally, it shifts all the text from the right of the search text box to the right also. And when it does that, I notice some of the text goes off the right margin until I select out of the search text box.
Same on my iPad, probably a problem only on tablet ?
Can you check if this is fixed now?
I just tried vertically and horizontally from chrome on my Samsung android tablet and clicking that my profile drop down menu still doesn’t expand the menu. Once clicked on it goes to my profile.
It does still expand fine from chrome on my iPhone and from chrome on my laptop.
Sorry, I’m just referring to the original issue with the scroll bars. For some resson it’s not detecting your device as touch capable is my guess.
The overflow is fixed, buuuut:
The top button alignement is now out of bounds, don’t you hate CSS ?
(removing the margin left and setting a fixed witdh of 137px solves it for me)
with the css mods:
The username part is variable width depending on your first name (or username). I’ll fix the hover state in an update later today.
Marking this solved since the original scroll bar issue is fixed.
@justin should i create a new topic for this issue? or do you already have that on your to-do list?
A new topic would be good. However, I’m not sure why your device is not reporting as touch capable, so I would need to take a closer look.
Sounds good. Will create a new one.