-
-
Notifications
You must be signed in to change notification settings - Fork 485
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
Appending to row doesn't work as it used to after the 1.2.0 update #595
Comments
Thanks for spotting this, @DavidLeBonk! Indeed, with ui.row():
for i in range(100):
ui.label(f'Label {i}') In 1.2.0 we replaces the default classes for certain elements with CSS style definitions in nicegui.css in order to avoid issues with contradicting classes after updating the Tailwind dependency. When replacing the classes "row" and "column" with the CSS equivalent from the Tailwind website, I forgot that "row" and "column" are also Quasar classes that wrap by default. So we can either leave it as it is and you need to enable wrapping with |
Thank you very much, adding |
Yes, it is an unintended change that can be fixed easily. And since we're planning a bugfix release today, we decided to re-introduce the auto-wrap for rows and columns. |
Sweet, I am happy I was of use! |
Ok, 537625b should re-introduce the old behavior. Will be released shortly. |
I just noticed that |
It looks like Tailwind classes overrule nicegui.css (which is desired), but nicegui.css overrules Quasar classes (which is undesired). And |
Loading nicegui.css before Tailwind and Quasar should solve the |
This was initially a YT comment but it got deleted, I'm guessing because of the Imgur links in the command so I made an issue myself here.
Hey I noticed that pre 1.2.0 I was able to append items to a row and have them drop down to the next row automatically if the page could not fit them, after 1.2.0 this is no longer the case, it now just carries on and adds a scroll wheel to the page, do you have any ideas on what changes within the 1.2.0 update could have caused this?
Examples:
1.1.11: https://i.imgur.com/AJvVpeT.gif
1.2.0: https://i.imgur.com/Wapxbao.gif
The text was updated successfully, but these errors were encountered: