-
-
Notifications
You must be signed in to change notification settings - Fork 105
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
[Enhancement] Upgrade pickers to Material M3 standards #558
Comments
Ok please wait with this change, i am refactoring it atm. For the modal partI think we should remove the integrated Modal feom the pickers completely and let the user decide where the picker sits. Wdyt? |
Agree with letting the user choose how the pickers should be rendered, having options "Modal - hovering in a popup" and "Docked - inline as a kind of dropdown below the field" available where only this latest options should present a new feature implementation. My idea of a "Docked" integration that we'd have the functionality the datepicker is visible when even the user is updating the main input field and represents the changes in real-time visually on the expanded picker |
… standards materializecss#558; implemented styling for in range (wip) materializecss#360
…ng text field if present materializecss#558
…; configured confirmation buttons to render when auto submit is false materializecss#558
…nce modal usage in component is deprecated materializecss#558
Additional enhancements (todo):
|
Before submitting...
Context
Pickers could use an improvement as they currently do not comply with the Material M3 standards
This would require SCSS styling refinement on the components
Currently the pickers can only be rendered as modals, would be nice if additionally we can implement docked rendering options as requested per #140
Current Behavior
No response
Expected behavior
No response
Possible Solutions or Causes
No response
Your Environment
The text was updated successfully, but these errors were encountered: