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
Vuetify: v1.3.1 Vue: v2.5.17 Browsers: Chrome OS: macOS Mojave
When using a v-card component in the opposite slot the small arrow pointer is facing the wrong direction.
Expected it to point into the middle of the timeline.
Pointed outwards.
https://codepen.io/jvanst/pen/zmJgao
Here is a solution, should I create a PR?
.v-timeline-item display: flex flex-direction: row-reverse padding-bottom: 24px &:nth-child(odd):not(.v-timeline-item--right), &--left flex-direction: row .v-card:before, .v-card:after transform: rotate(180deg) left: 100% .v-timeline-item__opposite margin-left: 96px text-align: left .v-card:before, .v-card:after transform: rotate(0) left: (0% - 4px) &:nth-child(even):not(.v-timeline-item--left), &--right .v-card:before, .v-card:after right: 100% .v-timeline-item__opposite margin-right: 96px text-align: right .v-card:before, .v-card:after transform: rotate(180deg) right: (0% - 4px)
The text was updated successfully, but these errors were encountered:
PRs are always welcome
Sorry, something went wrong.
be32ac2
Fixes #5397 (#5400)
02fd3ba
This fixes a css bug when using v-card in the opposite slot.
No branches or pull requests
Versions and Environment
Vuetify: v1.3.1
Vue: v2.5.17
Browsers: Chrome
OS: macOS Mojave
Steps to reproduce
When using a v-card component in the opposite slot the small arrow pointer is facing the wrong direction.
Expected Behavior
Expected it to point into the middle of the timeline.
Actual Behavior
Pointed outwards.
Reproduction Link
https://codepen.io/jvanst/pen/zmJgao
Additional Comments:
Here is a solution, should I create a PR?
The text was updated successfully, but these errors were encountered: