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
feat(VDataTable): forward arbitrary row events #15617
Conversation
This should probably just do something like #15592 with a special case for |
please add this feature, it's really necessary for v-data-table |
If this could be added to 2.6.10 i would travel from Canada and wash someone's dog, cat, bike, car, truck or windows where you live. * * Offer valid for a period of one year, shipping fees not included. Not valid in Alaska or Hawaii. |
This reverts commit 0e85a93.
I updated it to the way used for the Unfortunately, the order of the (existing) attributes provided by the events differ for the |
any chance for this to be merged soon? |
// TODO: for click, contextmenu and dblclick, the first argument should be data, | ||
// and the second argument should be the event, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't realise calendar was like this too. This is actually backwards, the first argument has to be the event so modifiers like .prevent
work.
name: 'touchend:row', | ||
source: 'v-data-table', | ||
value: `${dataString}, TouchEvent`, | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know if this is really necessary considering it takes any dom event now.
Description
resolves #13332
Motivation and Context
Allow to use the
mouseover
andmouseleave
event for data-table rows without having to completely rewrite the row-slot.How Has This Been Tested?
visually -> created a test markup and generated console outputs
Markup:
Types of changes
Checklist:
master
for bug fixes and documentation updates,dev
for new features and backwards compatible changes andnext
for non-backwards compatible changes).