-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Visual tweaks for the quick open drop-down. #3634
Conversation
border-radius: 0 0 4px 4px; | ||
box-shadow: 0 5px 10px rgba(0, 0, 0, 0.1); | ||
|
||
// using this to fix the spacing that breaks item seperators and had to use !important to override inline css |
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.
CSS comments use /* */
. I'll push a fix for this if this is the only issue.
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.
LESS supports // style line comments. The difference is that /* */ style comments in a LESS file are maintained in the generated .css file, where // style comments are stripped.
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.
Oh, I had no idea. As Emily Litella would say, "Never mind."
Hey--I like removing the separators, but there's some concern that it seems a bit hard to distinguish the individual list items from each other--it's a bit of a sea of text. A couple of things I tried:
Would it be appropriate to make the background gray and add striping similar to your mockup for the Find in Files results? There the striping seems to work well without making either the lighter or darker rows stand out too much. (BTW, I don't think we want to fix this by adding more padding between the items...want to keep the information density we have now.) |
np I'll give that a go. |
Updated the branch. |
I like the new look a lot! My only concern is that the selected color doesn't stand out enough. |
I'm OK with the subdued selected color. The selection is interaction based (moving the arrow keys or hovering w/ a mouse). So the movement and interaction draw your attention to the highlight. If there was no movement then I'd agree w/ @jasonsanjose, but I think it works here. |
.quicksearch-namematch { | ||
font-weight: bold; | ||
font-weight: 500; |
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.
This should use @font-weight-semibold
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.
This should use @font-weight-semibold
…quick-open-tweaks
…quick-open-tweaks
… the ref to ViewUtils. Removed .scroller-shadow. Thanks @jasonsanjose
Re removing the scroller shadow: what about when there's a ModalBar open at the top (e.g. Find)? Or a permanent menu bar (in inBrowser mode)? Do we still need a shadow for it to look good in those cases? |
@peterflynn ModalBars always sits on top of content so it will always have a shadow, so now only CSS is being used instead of JS. How do I go into inBrowser mode? |
Oh, I didn't see that you'd added a fixed shadow to ModalBar -- great! That same rule also covers inBrowser mode (that's what |
@larz0 - I think we ended up still having concerns about the selection highlight being too subtle. The issue is that (because of the way our widget works currently) you might start off with something other than the topmost item being highlighted (because if the mouse happens to be over the list when it opens up, the item underneath it gets selected even if you don't click on it). This probably isn't ideal, but fixing it would be difficult until we get a better widget implementation. So, it would be better if we could have a slightly colored highlight that was easier to see immediately against the striped items. |
No problem, try it now. |
Looks good--I merged it manually with master since there was a recent conflict. |
Visual tweaks for the quick open drop-down.
@njx pls review.