Vue-material: [MdTable] on md-selectable="multiple", @md-selected doesn't reliably fire

Created on 30 May 2018  路  7Comments  路  Source: vuematerial/vue-material

Steps to reproduce

ISSUE 1
open https://codesandbox.io/s/lrz0np1m0q in a new tab(needs to be fresh)
select 1 row
notice the selected row isn't displayed below(incorrect behavior)
unselect 1 row
select 1 row
notice the selected row is displayed below(expected behavior)

ISSUE 2
open https://codesandbox.io/s/lrz0np1m0q in a new tab
open dev tools
select 1 row
notice that there is no console log(incorrect behavior)
unselect row
notice that there is a console log(expected behavior)

Which browser?

Latest Chrome, Windows 10

bug

Most helpful comment

Hi, how about this issue ?
VueMateriel is still in active development or is being deprecated?
Thanks for your answer! 馃槃

All 7 comments

Hi,

i still have the problem:

https://codesandbox.io/s/o7n643p6zq

img

this is already fixed on dev branch

i think it is this change (this.$nextTick) in MdTable.vue

      syncSelectedValue () {
        this.$nextTick().then(() => { // render the table first
          if (this.MdTable.selectingMode === 'single') {
            this.MdTable.singleSelection = this.mdSelectedValue
          } else if (this.MdTable.selectingMode === 'multiple') {
            this.MdTable.selectedItems = this.mdSelectedValue || []
          }
        })
      }

see also the change in watch

      value () {
        this.syncSelectedValue()
        this.setWidth()
      }

hope that helps

As you can see here: https://codesandbox.io/s/o7n643p6zq?module=package.json, the sample code has been configured to use the dev branch.

I have also tested in a local environment (experiencing the same problem) and the package-lock.json show this:

"vue-material": {
    "version": "github:vuematerial/vue-material#383b25503e15f9d598ded3b3c0ca96b67ca856d6"
 },

ok, i tested it with yarn dev in the table examples and it works, but in the sandbox it doesn't :(

@railken @aburai Because dist isnt recompiled in dev branch, then using github version will use same old version.

@Samuell1 This issue seems to be duplicated a lot, but this answer (which works!) took a bit of searching to get to.

Could you build dev branch so we don't have to fork this just to build it?

Hi, how about this issue ?
VueMateriel is still in active development or is being deprecated?
Thanks for your answer! 馃槃

Was this page helpful?
0 / 5 - 0 ratings