-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Masterbar: clean up, component refactor, and move to gridicons #631
Conversation
Looks good so far, works good also |
I've to wrap up for the day, but so far I think I managed to:
Which sorted out automatically all the alignment issues. Missing:
|
Yeah as you noticed right now it's purely, mathematically, padded. We can do optical adjustment before merging once the core of this PR is done. The way the code is structured now should make it piece of cake. :) |
ffbdec0
to
318704c
Compare
d1f883e
to
a698d7c
Compare
Tested on Chrome, Firefox, Safari, IE11, Edge. Works. 👍 With the changes above now the notification dot works, and the style issues across the browsers all work. There are still two bugs:
And some style changes, as noted above:
|
A couple of quick observations just tested in Chrome today at various viewport sizes: 1: New post button doesn't have white fill when active, like current masterbar has: 2: Loading "pulse dot" overlays "new post" button in responsive mode. Not actually sure if this is unique to the new masterbar or if this also affects the old: 3: In a viewport width that invoke the mobile breakpoint, I couldn't get notifications to work at all. The button would be blue indicating it was clicked, but nothing would happen: I will test more later on, using devices and other browsers. |
Thanks! 1 — fixed, pushed a commit. So, summary of outstanding issues so far for ease of reading:
|
Fixed.
I discovered this is a bug present in production too. Not a blocker anymore for this PR. Opened an issue for it on #1611. |
|
||
getInitialState() { | ||
let newNote = false; | ||
let user; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Accidental tab here after let
should be space.
Looking nice! |
Great updates so far. Still not convinced about the no-label usability impact on mobile (even though visually it looks better) but I'm not sure how we'd measure that. Also -- I mentioned it in the previous issue -- this should not merge until the front end masterbar matches. Otherwise we run the risk of that being forgotten and having a huge lag. |
That's mostly a byproduct of the cleanup code. I thought to leave that in and see if we need to add them back in. At this stage, I'd merge it like this and revert later if we think it's better. But open to discussion.
True. This however goes far far far beyond the change of icons. So I feel it's rather important we push this as soon as it's ready — whatever this means. |
Cleanup: named z-index lost in rebase Identation fix Remove dead imports
Fix: force correct icon color on Firefox and IE11. Fix: active state on Editor Fix: show Notification panel showing in mobile breakpoint. Fix: spacing Fix: layout loader. Fix: align dot bubble position on mobile Fix: better visual rhythm for rightmost icons. Fix: active Notifications now disable other active states
remove masterbar-new-post remove masterbar-logged-out-menu
`section` gets initially passed as `false`, then becomes a string. Fix: hooked up Editor preload Cleanup: null and 0 are equivalent for ">" operator. Cleanup: made user "isRequired". Cleanup: shorter unseen notes code Fix whitespace Cleanup: isActive Cleanup: using ES6 default param Fix: the bar (fixed) now doesn't scroll away on mobile Fixes #1283
- Create "masterbar" folder. - Move sub-components. - Clean up layout folder. - Consolidate styles in the component. Remove old assets/stylesheet file for masterbar.
813e083
to
d84201f
Compare
Masterbar: clean up, component refactor, and move to gridicons
Was it intentional to not use the https://github.com/Automattic/wp-calypso/blob/d84201f/client/layout/masterbar/index.jsx#L69 |
Yes and No :) Yes: the masterbar was a hairball of very different components, each with different use and intent, so it has been normalized using all the same component. No: that logic bit was missed since it didn't appear as a branching function on the URL logic, but stacked as component. I'd re-add that at the masterbar level (which handles the logic), as a simple function. |
...or as you did in #1894 heh :) |
Looks like this change broke the
Logged bug in #1907 |
@seear What's the plan to update the black front-end masterbar with the same changes? I was under the impression this would be pretty soon after, but I'm still seeing the labeled version. |
It has been updated to Gridicons, the labels were kept mostly for ease of the first patch. We should align the labels off too now, with a follow-up patch on front-end. |
👍 |
@apeatling: frontend masterbar is now updated to match Calypso label/breakpoint behaviour. |
🎉 |
This issue is a deep refactoring of the Masterbar component.
Summary:
masterbar-item*
and derivates.flex
magic.To test:
Please take extra care in testing this one since it's a very important piece of the navigation.
Original Text:
Old:
New (24px):