mdc-select item not initialized from bound value about aurelia-mdc-web HOT 11 CLOSED

Aurelia treats native select in a special way, unlike non-native MDC widget. I'll see if I can do anything about it

from aurelia-mdc-web.

Version 1.1.6 does not need explicit mdc-list element. Please remove that or upgrade to v2 of the bridge.

from aurelia-mdc-web.

I cannot reproduce the issue in the gist
https://gist.dumber.app/?gist=4fb62077f5564275f96253b8e708314a

from aurelia-mdc-web.

It works when _availableStatuses is already initialized. But not when its lazy loaded like...

const loadAsync = new Promise((resolve, reject) => {
    window.setTimeout(() => {
        resolve( ["Katze", "passed", "Maus"]);
        }, 2000)
});

loadAsync.then((value:string[]) => {
    this._availableStatuses = value;
});

Unfortunately, I cannot edit your Gist because of rate limit hit.

from aurelia-mdc-web.

You can only set the value after the select is populated with options, otherwise it cannot find the corresponding list item.

from aurelia-mdc-web.

I've updated the gist for async load, no issue

from aurelia-mdc-web.

But shouldn't it work like that? https://gist.dumber.app/?gist=8204b93b878e0f8ad4f027ace68d06d9

from aurelia-mdc-web.

This cannot work. After activate the widget's value is set but there are no items to match that value with.

from aurelia-mdc-web.

But this is the way I used to implement that the Aurelia way using regular select elements.

I've updated https://gist.dumber.app/?gist=8204b93b878e0f8ad4f027ace68d06d9 by

<select value.bind="_selectedStatus">
     <option repeat.for="status of _availableStatuses" value.bind="status">${status}</option>
</select>

from aurelia-mdc-web.

Hopefully this will be sufficient. I've modified the binding observer to monitor mdc-list-item mutations.
It will wait for options before trying to pass the current value to the element.
But once options has been set at least once any subsequent options changes will pull the value from the element, possibly overwriting the current value if it is not present in the current list.

from aurelia-mdc-web.

But once options has been set at least once any subsequent options changes will pull the value from the element, possibly overwriting the current value if it is not present in the current list.

Doesn't sound wrong to me.

Thanks. I really apprecriate your passion.

from aurelia-mdc-web.