@Mickey58 you can chain the statement in your input event or do the value change inside the method. Ie @input="toggleNormkategorien, toggleAllNormkategorienState!=toggleAllNormkategorienState".

@s-molinari said in Dynamic v-model bindings in input fields do not update visually:

Hey Aldrin. He did put together a sandbox. https://codesandbox.io/s/codesandbox-app-5hxoc

Scott

Sry didnt see that as thread has become *tldr’ish, well that’s a start. Ty.

Tldr; as far as i can see above, theres nothing wrong in the components in question, its how you are structuring your data, imo i think you need some more time restructuring it or see and understand more how the component works, the docs should help. A codesandbox should also help so you can show what is working so far or whatnot, and in the end we can support you further.

Check The quasar codesandbox what @s-molinari linked above, imo would rather see a running code than code you posted in this thread, when at first look is rather complex or need restructuring*.

@Allan-EN-GB what a good life xD

@s-molinari that nullifies the class i mentioned above then. wonder why it was there tho? @rstoenescu

@s-molinari should be worth adding this in docs imo.

@qyloxe the click events are not being caught by the default slots because the parent div has no-pointer-events class. https://quasar.dev/style/other-helper-classes#Mouse-Related. can submit a report for this pls, thx. nvm, see @s-molinari 's workaround below.

@rconstantine can make a gh ticket for this pls, thx.

@jeimz173 those functionalities has been moved to QSelect now, https://quasar.dev/vue-components/select#Filtering-and-autocomplete async should be lazy https://quasar.dev/vue-components/select#Example--Lazy-autocomplete

my suggestion is to open a browser and inspect the element and make your changes in the css there to see which one looks best for you and then make your overrides.