We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Originally by @magi42
The v-table-resizer elements of all columns are all positioned at the right edge of the table row's element instead of the header cell's parent.
The problem seems to be caused by the rule for the header cell element in valo/components/_table.scss:
valo/components/_table.scss
[class^="#{$primary-stylename}-header-cell"] { position: relative; }
It previously also had "display: inline-block", but not anymore. Restoring the property makes it work nice again.
display: inline-block
Occurs in 7.3-SNAPSHOT.
Imported from https://dev.vaadin.com/ issue #14401
The text was updated successfully, but these errors were encountered:
Originally by @Artur-
Is this still an issue? Can't see any problems in the latest Valo test/demo
Sorry, something went wrong.
Originally by @jouni
Re-open if still an issue with the latest version from master.
I'm still getting it, although it's always possible that something else in my theme or elsewhere is causing it.
The issue occurs in Firefox. In Chrome it works just fine. I don't know about other browsers.
Indeed an issue in Firefox 24.7.0. Firefox Beta works as Chrome.
No branches or pull requests
Originally by @magi42
The v-table-resizer elements of all columns are all positioned at the right edge of the table row's element instead of the header cell's parent.
The problem seems to be caused by the rule for the header cell element in
valo/components/_table.scss
:It previously also had "
display: inline-block
", but not anymore. Restoring the property makes it work nice again.Occurs in 7.3-SNAPSHOT.
Imported from https://dev.vaadin.com/ issue #14401
The text was updated successfully, but these errors were encountered: