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

chore: make Filters clickable on mobile to open filters menu #12541

Merged
merged 2 commits into from
Mar 26, 2024

Conversation

nhsz
Copy link
Member

@nhsz nhsz commented Mar 22, 2024

This PR makes the "Filters" label clickable to allow opening filters menu on mobile

Copy link

netlify bot commented Mar 22, 2024

Deploy Preview for ethereumorg ready!

Name Link
🔨 Latest commit 9d3492e
🔍 Latest deploy log https://app.netlify.com/sites/ethereumorg/deploys/6602f721ee45a00008508ee1
😎 Deploy Preview https://deploy-preview-12541--ethereumorg.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Member

@wackerow wackerow left a comment

Choose a reason for hiding this comment

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

Looks good! Just left one question that I don't see as a blocker, but wanted to raise... can address separately.

Comment on lines 239 to 247
<Text
hideFrom="lg"
lineHeight={1.6}
fontSize="md"
color="primary.base"
textTransform="uppercase"
cursor="pointer"
onClick={onOpen}
>
Copy link
Member

Choose a reason for hiding this comment

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

Just curious, is there any reason we don't want to use a button here? Seems more appropriate from an a11y standpoint

Copy link
Member

Choose a reason for hiding this comment

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

Agreed. Now, we are basically turning this component into a button.

Copy link
Member Author

Choose a reason for hiding this comment

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

@wackerow It was defined in the design that should behave like a button but without the button styles. I think I can add the as={button} prop to improve a11y

Copy link
Member

Choose a reason for hiding this comment

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

Okay cool.. yeah that raising a small design system question... we have variant="link" for our buttons, but this will bold and underline the text (inconsistent with what we want here)... @nloureiro Should we have another variant that is even more simplified for buttons like this? Or should we convert this one to use the link variant styling?

Copy link
Member Author

@nhsz nhsz Mar 26, 2024

Choose a reason for hiding this comment

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

@wackerow do you think that could be a blocker for this PR or could be address later? I've added the as="button" prop.

Copy link
Member

Choose a reason for hiding this comment

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

Nope, not at all! We can address design system stuff separately, this works

@wackerow wackerow merged commit 200c3b3 into dev Mar 26, 2024
10 checks passed
@wackerow wackerow deleted the filters-label-clickable branch March 26, 2024 21:49
This was referenced Mar 26, 2024
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.

3 participants