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

Conversation

mattcosta7
Copy link
Contributor

@mattcosta7 mattcosta7 commented Dec 8, 2023

Changelog

Portal avoids createElement call on every render

New

Changed

Portal

Removed

Rollout strategy

  • Patch release
  • Minor release
  • Major release; if selected, include a written rollout or migration plan
  • None; if selected, include a brief description as to why

Testing & Reviewing

Merge checklist

Copy link

changeset-bot bot commented Dec 8, 2023

🦋 Changeset detected

Latest commit: 166fc0c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@primer/react Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Comment on lines +68 to +79
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
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?

Copy link
Contributor

github-actions bot commented Dec 8, 2023

size-limit report 📦

Path Size
dist/browser.esm.js 105.16 KB (+0.01% 🔺)
dist/browser.umd.js 105.68 KB (+0.01% 🔺)

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

@mattcosta7 mattcosta7 added this pull request to the merge queue Dec 8, 2023
Merged via the queue into main with commit c2a18b9 Dec 8, 2023
@mattcosta7 mattcosta7 deleted the avoid-every-render-div-on-portal-2 branch December 8, 2023 23:52
@primer primer bot mentioned this pull request Dec 8, 2023
@primer primer bot mentioned this pull request Dec 19, 2023
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.

2 participants