-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Refactor VisuallyHidden component to use ChakraUI #7724
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,43 +1,22 @@ | ||
import React from "react" | ||
import styled from "@emotion/styled" | ||
import React, { useContext } from "react" | ||
import { VisuallyHidden as ChakraVisuallyHidden } from "@chakra-ui/react" | ||
|
||
// "Accessibility/SEO Friendly CSS Hiding" | ||
// Source: https://css-tricks.com/snippets/css/accessibilityseo-friendly-css-hiding/ | ||
const Container = styled.span` | ||
border: 0; | ||
clip: rect(1px, 1px, 1px, 1px); | ||
clip-path: inset(50%); | ||
height: 1px; | ||
margin: -1px; | ||
overflow: hidden; | ||
padding: 0; | ||
position: absolute; | ||
width: 1px; | ||
word-wrap: normal !important; | ||
&:focus { | ||
background-color: #eeeeee; | ||
clip: auto !important; | ||
clip-path: none; | ||
color: #444444; | ||
display: block; | ||
font-size: 1em; | ||
height: auto; | ||
left: 5px; | ||
line-height: normal; | ||
padding: 15px 23px 14px; | ||
text-decoration: none; | ||
top: 5px; | ||
width: auto; | ||
z-index: 100000; | ||
} | ||
` | ||
import { ZenModeContext } from "../contexts/ZenModeContext" | ||
|
||
// Todo: Refactor to from isHidden boolean | ||
|
||
export interface IProps { | ||
children?: React.ReactNode | ||
isHidden?: boolean | ||
} | ||
|
||
const VisuallyHidden: React.FC<IProps> = ({ isHidden = false, children }) => | ||
isHidden ? <Container>{children}</Container> : <>{children}</> | ||
const VisuallyHidden: React.FC<IProps> = ({ children }) => { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we need to change the name of this component. This is not a generic component anymore. This is strictly related to zen mode. Would suggest calling this component There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Agree... just pushed a commit for this. I think this should be good to go now. |
||
const { isZenMode } = useContext(ZenModeContext) | ||
|
||
return isZenMode ? ( | ||
<ChakraVisuallyHidden>{children}</ChakraVisuallyHidden> | ||
) : ( | ||
<>{children}</> | ||
) | ||
} | ||
|
||
export default VisuallyHidden |
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.
Obviously out of scope for this refactor, but I disagree with how this component is architected.
If we wrap something as VisuallyHidden, we shouldn't also need to pass a boolean to hide the item we're wrapping.
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.
&& we might not even need a component for this at all if all we're doing is importing Chakra's primitive 🤔?
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.
Yes, this one is one of those components that we should remove completely and replace with the Chakra one.
My personal approach to this would be to use this PR to remove it and refactor the usage of this component in the entire codebase in favor of the Chakra one.
I'm fine as well if you want to take this middle ground approach. We could do the refactor later.
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.
Can do, the only place we use it is in Layout.tsx.
Are we fine with just conditionally rendering, or is there a smarter way to go about it 🤔
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.
Hmm looking into the code, I think it would be worth abstracting the zen mode state in its own component.
Inside
ZenMode
, you will have all of the logicThere 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.
Good idea. I will get to this when I have some free evening time this week.
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.
I think this is easier said than done given the
handleZenModeChange
inLayout.tsx
is passed to a provider. Will do some thinking here today.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.
I think we can just import this context though instead of this. Still ways to clean it up.