Q-Input and v-model.trim and clearable does not work on Q2

[zanzara]

IMO it seems to be a bug:
If i use this:

     <q-input
         v-model.trim="v$.bildUrl.$model" 
        :error="v$.bildUrl.$error"
        :error-message="getPicErrMsg(v$.bildUrl)"
         dense
         lazy-rules
         clearable
         autofocus
         :hint="$t('gwsCol.Bild.hint')"
   />

it throws me this error when I click on clearable:

If I use v-model w/o .trim it works.
Can anyone confirm? Or where is my mistake? (it works in Q1)

(Info: » Pkg quasar........ v2.0.3 » Pkg @quasar/app... v3.0.4 )

[ontwikkelfabriek]

@zanzara

Please post the script part of the code. Even better create a codepen.io to demo your issue for better support.

[zanzara]

@ontwikkelfabriek and i tried it on a vanilla chromium. The same error.
IMO this got nothing to do with private mode or other plugins. To me it's crystal clear an error so far.

[zanzara]

@ontwikkelfabriek So let's go back to start. One last question:
Can you confirm , that you hit the x-cross-clear button on the right side of the input-field in your test?
(Only then I get the error)

[ontwikkelfabriek]

@ontwikkelfabriek

Awww sorry. No I never clicked on that button. When I do, I get the same error.

Clicking the cross must make the model value null or undefined instead of empty string....bug in clearable property?

Can think of a way to work around the bug yourself? ( use a append right slot , create your own clear button with icon and with event handler that will set the v-model to '' ( empty string).

[zanzara]

@ontwikkelfabriek The question is, should clearable property really make the model value null?
Shouldn't it be more like setting it to '' emtpy string?

I'm convinced this is a bug in clearable property.
So I would transfer this discussion post here to to the issue tab (also beacuse in Q v1 this works w/o raising an error).

For the moment I refactored al my v-model.trim s to v-model only, where q-input has this prop. Maybe there could be soon a fix, then I'll reject my changes.

[ontwikkelfabriek]

@zanzara

I'm convinced this is a bug in clearable property.

Yes me too.

You could be very helpful to Quasar community by creating a Github issue for this...

[qxygene]

any update on this?

[pdanpdan]

@qxygene interesting, your very helpful multiple contribution missed the only place where there was an update
#10376 (comment)