-
Notifications
You must be signed in to change notification settings - Fork 72
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
Autocomplete: Add "position" property to control component placement relative to the element #2801
Comments
Hello @prashanth-offcl! Thanks for opening an issue. The Modus core team will get back to you soon (usually within 24-hours) and provide guidance on how to proceed. Contributors are welcome to participate in the discussion and provide their input on how to best solve the issue, and even submit a PR if they want to. Please wait until the issue is ready to be worked on before submitting a PR, or you can reach out to the core team if it is time bound. For trivial things, or bugs that don't change the expected behaviors and UI, you can go ahead and make a PR. |
Related to #2783 |
Prerequisites
Proposal
Introduce an optional 'position' property that allows the component to be positioned relative to the current element. it should accept various positioning options such as top, bottom, left, right, and auto, similar to how tooltips are positioned.
Acceptance criteria:
Motivation and context
By introducing a dedicated position property, we can simplify the process and make it more intuitive for developers to align components accurately. This change will improve the flexibility and usability of the component, ensuring that it integrates seamlessly with various layouts and use cases.
What is the issue regarding ?
@trimble-oss/modus-web-components
Priority
High
What product/project are you using Modus Components for ?
modus-internal
What is your team/division name ?
modus-internal
Are you willing to contribute ?
None
Are you using Modus Web Components in production ?
No response
The text was updated successfully, but these errors were encountered: