[Suggestion]: portals caveat
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
Summary
The problems solved by portals can also be solved by the dialog element, popover API and anchor positioning.
I think it is worth mentioning that on the page less people think the only approach is to use portals.
Page
https://react.dev/reference/react-dom/createPortal
Details
I wrote about it here: https://fullystacked.net/portal/
I don’t think native popovers are perfect. There will probably always be a need for this portal API, but I think the main example shouldn’t be a modal. That genuinely is better solved with the native HTML element.
I’m not suggesting a large new section, just a brief note to say there are other approaches.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the React DOM createPortal reference page linked in the issue and review its modal example and surrounding explanation. Add a brief note acknowledging dialog, popover, and anchor positioning as native alternatives, then verify the page clearly presents portals as one option rather than the only approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, react
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100