primefaces / primefaces/primereact
how to override the method PrimeReact uses to position the overlay
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 8.3k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Hello, I am developing a map using the ReactFlow library. This library uses a div where it renders the map. It is possible to pan and zoom on the map, but it does so with CSS transformations. I am using PrimeReact's OverlayPanel, but I have encountered a problem. If the appendTo of the overlay is set to "self", it moves correctly with the map and applies the same zoom as the map since it is contained within a div to which the CSS transformation is applied. The problem is that it does not position correctly on the element that opens it. Is there any way to override the method PrimeReact uses to position the overlay and take into account the transformation of the parent container? Or, on the other hand, how could I position the element correctly if the container has a transformation? If the appendTo is set to the default, it positions correctly but becomes disconnected when panning or zooming the map.
Reproducer
No response
PrimeReact version
10
React version
17.x
Language
TypeScript
Build / Runtime
Create React App (CRA)
Browser(s)
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
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
Start with the OverlayPanel positioning behavior and its appendTo options in the ReactFlow transformed-container scenario. Compare the self and default append targets, then create a reproducible case for pan and zoom alignment; done means the overlay remains correctly positioned or the supported limitation and workaround are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100