Oh, thank you! Slots are so powerful!

I use QSelect with autocomplete function and chips input. I didn’t find any options to change chips color from grey…Is that possbile?

What I actually did now is placed my QInputs inside <q-item-section><q-item-label><q-radio>…</q-radio></q-item-label></q-item-section> rather than creating a sibling <q-item-section><q-item-label>…with the form fields inside.This way QList with tag=“label” does’t seem to cause any trouble. If that does not contradict any of Quasar’s principles for now I’d go on with that option.

https://codepen.io/Solarwake/pen/VwZywgb
I used the same model for all inputs in this sample. It worked the same with different models on each input or with just one input displayed only with the active QRadio-QItem coupling. The same behavior with QSelect used with autocomplete input.

Also, I found that inputs placed inside q-radio do not show that queer behavior. However, I’ve been using the template I posted in codepen because it seemed more convenient as I was rendering a small form with a few inputs inside the selected QItem.

Good day.
I use tag=“label” property on QList (to encapsulate QRadio in list items, if this information is essential). I placed a few QInput components inside QItems in the list. However, I cannot focus on QInput fields when I have tag=“label” property. It occurs this way:
when I just click on the input field the @input even occurs immediately, the label (float-label) jumps up for a moment and then returns to its initial position and the input field loses focus. And I cannot type anything in the input field (I can only do it if I click on the field and keep my mouse key pressed down).

I’ve been using the same construction in the previous Quasar version and it worked just great.
I’m not sure whether it’s a bug or my lack of understanding how click event propagation works.

Thank you.

Oh, my bad(( That’s written on pink…Thank you! I could do without q-field actually but I found that in the new version Quasar generates a custom id on every q-input element, like ‘id="qf_3061d64c-aa2d-4392-7fcf-6e019645a100’. With the previous Quasar version I used to add my own Id property either to QField or QInput which was very convenient to run quick tests. Adding my own id to QInput won’t overwrite the one genetated by Quasar (but it for works for QField). So I assume it’s not a good idea to attempt to do so at all as Quasar needs its own generated ID for better control over components…

I’m trying q-field and q-input combination on v1.1.0:

      <q-field
      :value="username"
      class="col-12"
      label="lemail"
      id="emailField"
      filled >
        <template v-slot:control>
          <q-input  
          class="col-12"
          v-model="username" 
          clearable
          color="orange"
        />
      </template>
      </q-field>
      
      <q-field
       :value="username"
       label="password"
       id="passField"
       filled
       class="col-12">
        <template v-slot:control>
          <q-input
          class="col-12"
            v-model="password" 
            color="indigo"
            type="password"
            clearable
          />
        </template>
      </q-field>

And I have at least 2 issues so far. 1. double-inderline 2. double fill-box (from ‘filled’ property). Moving the ‘filled’ property from q-field to q-input component removes the second box, but the float-label floats up outside the fill-box boundary then. Removing the <template v-slot:control> wrapper fixes the double-undeline issue but I figure this is not the right way at all. Did anyine have similar issues?

I found a similar topic dealing with double-inderline after update but I’m using a brand new project.

Good day!
I want to use q-modal in ‘maximized’ mode so that it cover the entire screen. And slide in from left side. However, if I add a ‘position’ property the modal widnow is no longer ‘maximized’: it does spread 100% screenwide but the height is minimized. A bug, a feature or do I need extra information? I’m using v0-17 so far.

@s.molinari, yes, I’ve been trying to avoid using slots and from what you say I see this is the only way if I want to proceed with ids. Thank you!