Skip to content

avoid creating a div on every render in portal #4037

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

Merged
merged 1 commit into from
Dec 8, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/weak-balloons-search.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'@primer/react': patch
---

Portal avoids useless createElement
23 changes: 13 additions & 10 deletions src/Portal/Portal.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -65,14 +65,18 @@ export const Portal: React.FC<React.PropsWithChildren<PortalProps>> = ({
onMount,
containerName: _containerName,
}) => {
const hostElement = document.createElement('div')
const elementRef = React.useRef<HTMLDivElement | null>(null)
if (!elementRef.current) {
const div = document.createElement('div')
// Portaled content should get their own stacking context so they don't interfere
// with each other in unexpected ways. One should never find themselves tempted
// to change the zIndex to a value other than "1".
div.style.position = 'relative'
div.style.zIndex = '1'
elementRef.current = div
}

// Portaled content should get their own stacking context so they don't interfere
// with each other in unexpected ways. One should never find themselves tempted
// to change the zIndex to a value other than "1".
hostElement.style.position = 'relative'
hostElement.style.zIndex = '1'
const elementRef = React.useRef(hostElement)
const element = elementRef.current
Comment on lines +68 to +79
Copy link
Contributor Author

Choose a reason for hiding this comment

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

since we only used the ref, which is created on the first render, we can just create it on the first render.

this is still not SSR safe, however, and we should probably change this to account for that, but at least we're not wasting memory for no reason?


useLayoutEffect(() => {
let containerName = _containerName
Expand All @@ -87,15 +91,14 @@ export const Portal: React.FC<React.PropsWithChildren<PortalProps>> = ({
`Portal container '${_containerName}' is not yet registered. Container must be registered with registerPortal before use.`,
)
}
const element = elementRef.current
parentElement.appendChild(element)
onMount?.()

return () => {
parentElement.removeChild(element)
}
// eslint-disable-next-line react-hooks/exhaustive-deps
}, [elementRef])
}, [element])
Copy link
Contributor Author

Choose a reason for hiding this comment

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

element is stable, so this is the same. I kind of wonder if the lack of exhaustive deps here indicates other issues, but ignoring that for now since this pr is keeping identical behavior characteristics, with just a bit less waste


return createPortal(children, elementRef.current)
return createPortal(children, element)
}