Skip to content
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

feat(Dropdowns): Clockface 4 dropdown updates #876

Merged
merged 5 commits into from
Oct 19, 2022

Conversation

ChitlangeSahas
Copy link
Contributor

Closes #838

Couple screenshots:

SelectDropdown:

Screen Shot 2022-10-17 at 9 22 16 PM

TypeAheadDropdown:

Screen Shot 2022-10-17 at 9 27 58 PM

CreateableTypeAheadDropdown:

Screen Shot 2022-10-17 at 9 28 43 PM

MultiSelect:

Screen Shot 2022-10-17 at 9 29 16 PM

  • Updated documentation to reflect changes
  • Added entry to top of Changelog with link to PR (not issue)
  • Tests pass
  • Peer reviewed and approved
  • Signed CLA (if not already signed)

@ChitlangeSahas ChitlangeSahas changed the title Clockface 4 dropdown updates feat(Dropdowns): Clockface 4 dropdown updates Oct 18, 2022
@ChitlangeSahas ChitlangeSahas changed the base branch from master to clockface-4-master October 18, 2022 04:30
Comment on lines +56 to +57
margin-right: 2px;
margin-left: 1px;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These two stick out, but they're just to please the absolute positioned, Scrollbar library we're using

Copy link
Contributor

@hoorayimhelping hoorayimhelping Oct 18, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can this be solved using position and left and right rather than with using margins? Semantically, there's a big difference between position and margin, and we should use positioning for laying things out, and margins for when we need space around an element. I'm not super familiar with how this is used, though

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got you! I'll try that!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Screen Shot 2022-10-18 at 8 19 39 AM

It still cuts off the right end of it, I think this is what is happening:

IMG_D4759C8952C6-1

So, when I add the margin, the border falls under the available space.

Unfortunately, I am not able to change the width of the inner wrapper, since it's controlled by the react-custom-scrollbar library.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was always a problem, but we never noticed because we didn't use borders as an indicator for being selected. Now that we use the border, we see that the 1px of the right is cut off.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it causing problems to have the border? julia and i also discussed maybe not needing a background color at all on selected items. we included it because that's what we have now—adjusted to be lower contrast so it's less distracting—but i think the selected state for the radio buttons and checkboxes has enough contrast that we might not need the background color+border as well. let me know what you think. @ChitlangeSahas @hoorayimhelping @juliajames12

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently I implemented it in the way figma looks, with no issues. But if we decide to remove the border+background, let me know I can make a future ticket and address that! 👍

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

talked to sahas—it's a big of a bigger project to reevaluate these, so we'll keep it as-is for now and tweak it later if we find we need to once we test it out

Comment on lines +225 to +230
@include buttonColorModifier(
$cf-turquoise,
$cf-turquoise,
$cf-grey-1,
$cf-grey-1
);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just ran prettier, hence the diff.

@ChitlangeSahas ChitlangeSahas marked this pull request as ready for review October 18, 2022 04:32
@ChitlangeSahas ChitlangeSahas requested a review from a team October 18, 2022 04:32
@@ -69,10 +72,18 @@ $dropdown-item--padding-v: $cf-space-2xs;
.cf-dropdown-divider {
@include dropdownItemStyles();
font-weight: $cf-font-weight--medium;
text-transform: uppercase;
color: #88889b;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this is just a divider - does text-transform: uppercase have any effect?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Screen Shot 2022-10-18 at 9 17 47 AM

The dividers have text, optionally 👍

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha - thanks!

@ChitlangeSahas ChitlangeSahas merged commit 0c4cb93 into clockface-4-master Oct 19, 2022
@ChitlangeSahas ChitlangeSahas deleted the clockface-4-dropdown_updates branch October 19, 2022 16:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clockface 4.0: Dropdowns
4 participants