Version 5.0.0, released 29.08.2022
MDB 5.0.0 brings many improvements, mostly focused on updating our design system.
Design updates:
First of all - our basic color palette has been updated. We toned down our colors to be less flashy and more elegant and subtle. This affects virtually all of our components, so be aware of this before upgrading your project to MDB 5.0.0.
Read
to learn more about new palette.
Breaking changes:
- Our
have a slightly colorful shadow now. For this reason buttons with custom colors (like
) cannot use base modifier classes like .btn-primary, .btn-danger, etc (because they will cast a shadow of a color that may be not consistent with the background color of the buttons). In this case we suggest to remove the modifier class and and add .text-white class to fix the problem with the text color.
- We implemented
, so the secondary button changes its color and loses its shadow. We also added a new, tertiary button.
-
that uses secondary buttons now require .shadow-0 class to fix the problem with a shadow by default added to the .btn-group class.
- We replaced classes bg-grayish, .text-grayish, and .link-grayish with classes .bg-secondary, .text-secondary and .link-secondary
Fixed & improved:
- Improved
- Improved existing
and added new examples
- Improved
design
- Improved
design and added new examples
- Improved
and
design
- Fixed
bug on mobile
Additionally:
We have also published a
and a few design improvements in our docs. Let us know how do you like it now!
In addition to the design improvements, MDB 5.0.0 introduces several other significant changes.
Breaking changes:
After checking how our events work in the Table editor plugin, we came to the conclusion that this requires Breaking changes. So far, using e.preventDefault() in our events was not supported.
We changed the behavior of events to trigger them before performing a given action and allow to use e.preventDefault() - for example, to prevent the addition of a row that contains data that we do not want.
We also decided that maintaining two similar events does not make sense. Therefore, we are removing the updateEntry event. From now on, event edit returns the row that has been edited, removed or added.
-
- updateEntry.mdb.tableEditor event removed
- update.mdb.tableEditor event emitted after editing, addition or deletion row
- add.mdb.tableEditor event emitted before adding row
- edit.mdb.tableEditor event emitted before editing row
- delete.mdb.tableEditor event emitted before deletion row
Fixed & improved:
- Fixed
animations on div
- Fixed
init via jQuery
- Fixed
padding for inline pickers
- Fixed elemennt width change when
is added
- Fixed
pagination with less then 10 rows per page
- Fixed
default selected options active class issue
- Fixed
console error on mobile after click ok button, without selecting time
- Fixed
remove listener after dispose issue
- Fixed
addItem method
- Fixed multiple values issue in
- Fixed
duplicated delete event
- Added possibility to set
initial input value