You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have recently switched to PopperJS in my own Projects PopperJS or now called https://github.com/floating-ui/floating-ui
I already saw that Bootstrap is using it for a long time. In Materialize we currently have our own implementation with the Dropdown Component. But what do you think about switch/implementing to this Library since it is well supported and
already after 1 week i see nice improvements.
This solves nested Dropdowns for me, as they were not possible with the current setup.
Here you can see an example:
What do you guys think? Should we implement it?
The text was updated successfully, but these errors were encountered:
Yess you are right, I also like to have no or less dependencies...
We can fork or implement it as a copy, so we dont have to rely on the project.
Also it is very small, so i see not much of a issue here. We can just copy the JS-File.
Also we have dependencies from waves.js as i remeber.
I dont know why Bootstrap is using it as a seperate CDN-Link implementation. Maybe for saving the space.
I have recently switched to PopperJS in my own Projects PopperJS or now called https://github.com/floating-ui/floating-ui
I already saw that Bootstrap is using it for a long time. In Materialize we currently have our own implementation with the Dropdown Component. But what do you think about switch/implementing to this Library since it is well supported and
already after 1 week i see nice improvements.
This solves nested Dropdowns for me, as they were not possible with the current setup.
Here you can see an example:
What do you guys think? Should we implement it?
The text was updated successfully, but these errors were encountered: