This has been merged and will be included in the next tagged release.
We intentionally leave the container full width for developers to adjust and control as they see fit on a per theme basis.
Marking this fixed with the most recent tagged relase.
@pixelwhip → Please review this update and the function changes, currently we are just suppressing the JS API warning.
This has been merged in and will be included in the next tagged release.
We had a working meeting getting the component updates pulled in.
This has been merged in and will be included in the next tagged release.
This has been merged in and will be included in the next tagged release.
This has been merged in and will be included in the next tagged release.
This has been merged in and will be included in the next tagged release.
Looks great! This has been merged in and will be included in the next tagged release.
This has been merged in and will be included in the next tagged release.
This has been merged in and will be included in the next tagged release.
This has been merged in and will be included in the next tagged release.
This has been merged in and will be included in the next tagged release.
This has been merged and will be included in the next tagged release.
This has been merged in and will be included in the next tagged release.
Thanks for your help and for opening an MR, this has been merged into the 5.x branch and will be included in the next tagged release.
Closing this in favor of component specific tickets to keep this scoped better.
The current blockers for stable are updating our changelong & project readme in addition we have decided to standardize our prop names within components.
Remaining tasks
- Clean up codebase & formating
We have decided to move away from supporting a mixin and instead will leverage utility classes by adding buttons.scss to 01-elements In addition we will duplicate styles for inputs into forms.scss
We have determined this as a blocker for our stable release.
We have determined this as a blocker for our stable release.
We have decided to postpone this development, with the update to build tools this past year this is not an immediate need.
We have decided to remove component prefixes on prop names and have created dedicated issues to address this change.
jldust → created an issue. See original summary → .
We are going to have a follow up conversation related to possibly removing these prefixes.
We are going to have follow up conversations related to handling JS within Prototype.
This has been merged in and will be included in the next tagged release.
Thanks for the updated component, this has been merged in and will be included in the next tagged release.
This has been merged in and will be included in the next tagged release.
Thanks for all the feedback and edits, this has been merged in and will be included in the next tagged release.
This was addressed in Nested Menus with 💬 Nested Menus with Active
Use cases we need to test for:
- Menu items with nested menus using default for label
- Nested menu with using elements other than span
- Nested menu with button menus in same list
This is the first pass on adding support for nested menus without controls, there are several use cases that need to be discussed before this is approved.
Thanks @philip_stier → this looks great!