lindespang
lindespang
Thanks for using MatBlazor, I'll take a look at it tomorrow.
@allnet Hi, will take a look at it over the weekend and hopefully fix. Could not find the time yet. The author of this repository @SamProf has a Patreon page...
I've identified the issue and will submit a PR in the near future.
(Copying from previous closed issue) Seems as there was a problem with the MDC select Component that was recently fixed https://github.com/material-components/material-components-web/pull/5870 Unfortunately it just missed the 6.0.0 release. I think...
... Hmm but I think I found something that looks weird anyway in MatSelect, reporting back shortly..
Will wait until new MDC Select, sorry. The workaround is to have your collection initialized before supplying it to the MatSelect since this problem appears if you change the collection...
@doyce I understand. Depending on the frequency of the user interaction it might be feasible to re-render the component? @allnet Glad to hear it. Not right now since I have...
@allnet It's not supported in the MatBlazor API, but you can alter the `` elements with Blazor syntax to get what you want. https://blazorfiddle.com/s/fffkrbjd In my example it's inline style...
I'm pretty sure this is a duplicate of #494. A workaround (if feasible for your project) is to wait untill you have your results from the API until you render...
@americanslon Maybe you can render a disabled MatSelect placeholder which doesn't have any bindings until your api call returns? Makes sort of sense since the user can't select anything at...