On OS X 10.9.5 and Chrome stable the right portion of the menu goes off screen when zoomed in.
1 Like
It is ā and it looks way better. Thanks!
1 Like
The latest commit definitely looks and feels much nicerā¦ but position: fixed; makes for a rough experience. I imagine thatās temporary and in the process of getting addressed?
3 Likes
Yup the latest build, deploying shortly has it changed to absolute following a suggestion from @Sam.
1 Like
Just grabbed the latest commit on my instance. Feels much better! I also like how the hamburger menu no longer has a transition. I wanted to remove the transition from the other glyphs to match, but I couldnāt find the styles. Are you doing them in JS instead of CSS?
1 Like
So, since all the screenshots seem to focus on the upper edge of the new menu, let me be the one to tell you that this is quite silly
Itās not full height for me and I even get a scrollbar. This is not me messing with the window, either (resizing, etc).
Windows 10
Opera 30.0
1366x768 laptop-resolution.
Filed Under: Not sure if all fixes are deployed. I refreshed before taking the screenshot
Addendum: If this is the way it is supposed to look, I apologize. I just have the feeling this is not how itās supposed to look like.
5 Likes
Yeah @eviltrout I think there is a tiny bit too much margin from the bottom.
Similarly we need to adjust to content size here, otherwise you get this which looks real odd
6 Likes
Itās an improvement either way. Thanks for listening to our feedback 
1 Like
Not sure if this should be a separate 
report, but the = shortcut to open the hamburger no longer functions.
(Firefox 40 & Chromium Version 44.0.2403.89 on Ubuntu Gnome 15.04.)
6 Likes
This must have happened recently, as I tested that when it was the slide out menu and it worked then. 
Good catch!
4 Likes
Didnāt have much time to comment the other day, but the changes made so far are pretty much exactly what I would suggest ā the structure disconnect with the slideout on desktop was real weird!
Iām not going to jump to necessarily removing thingsā¦ some of this stuff is ābetter to have it and not need it than to need it and not have itāā¦ but letās take a look at organization.
Housekeeping stuff: About, FAQs, Keyboard Shortcuts
Taxonomy: users, badges, tags, categories
āLatestā is a bit odd on its ownā¦ are people using that? I generally click on the logo to go back to the latest page (though this behavior differs depending on preferences, and maybe thatās ok?)
Menus could be
- Search (keep as is - expanding it inline along the buttons is a cool ideaā¦ but I think the āsearch this topicā and āoptionsā are nice and warrant the extra click)
- Hamburger
- About
- FAQs
- Keyboard Shortcuts
- Badges
- Users
- Tags
- Categories
- User (combining these is interestingā¦ I like the mockupā¦ but does it downplay notifications too much?)
- Profile
- Preferences
- Log Out
- Messages
- Notifications
- Admin (may be worth setting apart and/or expanding?)
- Dashboard
- Site Settings
- Flags
- Needs Approval
- Akismet
3 Likes
Great feedback
This is one thing that we decided to keep just on the user page, inviting people to āLog Outā every time they open notifications is super weird.
I think its really interesting as an experiment to tease out admin from the hamburger. It would allow us a more comprehensive admin menu right from the header. A direct link to āsite settingsā for example would be mighty useful to me.
2 Likes
There is also a strong need to jump to Top, New, Unread directly which is not listed here.
4 Likes
For me as well. So much so that I have a plugin that adds it to the hamburger menu.
Itās localhost development so I use it extremely often.
I canāt see it being as useful for an established production site, but maybe.
1 Like
New (3) Unread (4) in the user drop down may fit better than in the hamburger
I honestly feel About, FAQs and Keyboard Shortcuts should be at the bottom of the dropdown/slide out menu all on the bottom line. For the most part those are things that would live in the footer but arenāt possible with infinite scroll. Having them at the bottom of the menu makes it easy to find them contextually and also leaves space for more important and more used links/actions.
I think joining them might be valuable as well, or at least user and current hamburger. Having notifications be itās own thing is good since I feel there is more that can be done as Discourse is polished and made more active.
As far as the search icon, maybe it isnāt a choice of icon that you have to click over input already available. How about an input that is smaller (not much larger than the icon itself, that when you click into it expands to take up more space and gives you the full search input. Iāve seen other sites do that and it was really intuitive and easy to use.
2 Likes
Yeah we did the search thing back at stack overflow. I really like it. (but you would lose the ability to pick context prior to searching that sucks a bit, unless we do a big revamp.)
Several people have said this and I hate saying āimpossibleā. It would just require some design changes, such as an always-visible footer (like the current header). Iām not saying I like that idea, but I canāt stand starting with the presumption of impossibility. 
Same here. I like to think that āWith code, anything is possibleā
In a way, the composer is like an on-demand footer.
I donāt know if that precludes there being a ānav footerā
Jumping in late to the feedback party here.
Our discourse instance is used a lot on mobile and a full height menu with adequately sized menu items is very important. Currently I often find myself second guessing touching any menu item in the hamburger menu.
One example of good and scalable top menu design I came across is the one on 99designs.com.
The hamburger menu is on the left hand side and is expanded based on the available width (scales perfectly between mobile and desktop).
User notification and profile management is on the right hand side and also offers a popup or slide out based on the canvas width
3 Likes