Skip to content
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

Floating UI: Add detectOverflow configurable collision boundary #16879

Open
8 tasks
Tracked by #14139
tay1orjones opened this issue Jun 27, 2024 · 1 comment
Open
8 tasks
Tracked by #14139

Floating UI: Add detectOverflow configurable collision boundary #16879

tay1orjones opened this issue Jun 27, 2024 · 1 comment
Assignees
Labels
planning: umbrella Umbrella issues, surfaced in Projects views type: enhancement 💡
Milestone

Comments

@tay1orjones
Copy link
Member

tay1orjones commented Jun 27, 2024

In certain situations consumers may need to customize the boundary/element used to detect collisions. One example of this might be the modal - components like Popover may need to reflow based on the bounds of the modal content container, and not the viewport.

To this we can implement the detectOverflow as a middleware and add props for consumers to pass in their own element and/or padding.

This will need to be done for every component that supports floating ui autoAlign:

Tasks

@tay1orjones tay1orjones changed the title Evaluate if we need to allow consumers to configure floating-ui themselves by exposing more API (additional props? attributes?) and also allowing them to configure the container element to control reflow more granularly/locally than the viewport Floating UI: Add detectOverflow configurable collision boundary Jun 27, 2024
@tay1orjones tay1orjones added planning: umbrella Umbrella issues, surfaced in Projects views type: enhancement 💡 labels Jun 27, 2024
Copy link
Contributor

Thank you for submitting a feature request. Your proposal is open and will soon be triaged by the Carbon team.

If your proposal is accepted and the Carbon team has bandwidth they will take on the issue, or else request you or other volunteers from the community to work on this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
planning: umbrella Umbrella issues, surfaced in Projects views type: enhancement 💡
Projects
Status: ⏱ Backlog
Status: Now
Development

No branches or pull requests

2 participants