Good day. I am using a bluetooth keyboard for typing in my Android smart phone and is encountering this weird behavior: in q-input, the cursor automatically goes on the first character of the previous word you typed if there is a spelling error, preventing you from typing the next word unless you type the correct English word.

I would like to get rid of this feature off since not all words that I type is in English. I tested it on websites with html only and seems that it also occurs so I don’t think that Quasar has something to do with it but I am really in a bind right now as I am encoding my study materials on my phone.

I already tried turning off autocorrect, autocapitalize, autocomplete, and spellcheck but to no avail.

I hope someone can help me with it. Thank you very much.

@metalsadman I found the bug now. An obscure function in my logic is causing the issue. Thanks again for your time

@metalsadman Here’s the codepen: https://codepen.io/maple-syrup/pen/vYOyved
Seems that I can’t replicate it also here. I’ll verify the versions of my packages. Or I might have missed out something in my code. Thank you for informing me about having it in codepen.

Btw, I tried restyling the q-chip here instead of using truncation. Might be of help to others if they want this kind of style.

@metalsadman i’m away from my computer at the moment. I’ll make one later. Thanks!

Good day. I have a q-select with q-chip directive and i have dynamic entries wherein a comma is present. As with the image attached, it separates the entry into two as its default behavior. Is there any way or workaround to specify a different separator for q-select? Thanks! As with the image, it should be “/extella/Intro to Matter, Energy and DC/1582391910131.jpg”

Finally found the issue. Seems that I need to put the following code in both created and activated life cycle hook:

this.categoryId = this.$route.query.categoryId

I don’t know the reason behind but it’s now working.

I also updated the description and the code.

@metalsadman I’ve gone back in my work after a few hours and seems that it’s not the browser cache that is causing the issue, the problem is still there. Seems that earlier is just a glitch.