-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Table: equal behaviour for height and max-height #14660
Table: equal behaviour for height and max-height #14660
Conversation
Deploy preview for element ready! Built with commit fbdd002 |
@arthurdenner It works for me. |
I checked the commit records of |
There is another bug, set the table of max-height and the height is wrong. |
Can confirm, all tables' heights are broken |
When max-height is string, it will cause another bug. https://codepen.io/ziyoung/pen/qwvryL |
There is another bug,want it back in the next release |
Why did you do that, this leads to bugs |
bodyHeight returns the default empty height in case of data loading delay. |
I also have this problem height:'80vh' does not work ! so I used old version '2.7.2' it's ok |
Closes #13751.
This PR is an attempt to close the referenced issue since I'm not sure if it breaks something...
Since the
max-height
is calculated this way, if you specify it with a unit other thanpx
(an integer), it doesn't calculate properly, therefore, doesn't show the scrollbar.I looked into why it's calculated like that and couldn't figured out, so I tried to replace it with the same calculation used for
height
and it worked as expected. Even this example, created in the PR that originated themax-height
feature, just worked as before.I checked the documentation after changing the calculation and all the examples are working as before, so it seems to me that the change doesn't break anything, but please review it carefully since I'm not aware of all the edge cases covered by the current calculation.