awesome quasar, thanks!

Can’t figure out how to navigate to next input after enter a value using virtual keyword on mobile (without tap on next input, consider a complex form)
https://jsfiddle.net/572oLxyu/
tabindex :attributes="{tabindex: ‘n’}" does not make any difference
using q-field requires 2 tabs in desktop, same behavior on mobile

any tip apreciated, thanks!

hi
i used document.body.style.zoom property to apply some customized flexibility for visual accesibility in responsive webaps, it is easy and get very good results (in Chrome at least).
Recently i´ve tried it on iPhone (Safari) without so good results.

How do you solve size related accesibility issues? (i mean for people around 45 years old… )
thank you!

awesome quasar, thanks!

Can’t figure out how to navigate to next input after enter a value using virtual keyword on mobile (without tap on next input, consider a complex form)
https://jsfiddle.net/572oLxyu/
tabindex :attributes="{tabindex: ‘n’}" does not make any difference
using q-field requires 2 tabs in desktop, same behavior on mobile

any tip apreciated, thanks!

In production, i think must reload.
Now i see damosse31 said “avoid ask user press F5…”, shure, you can ask kindly to finish current work and then reload, with a popup or so…
Thank you!

Thank you!
I never used webpack but it worked without ctrl+F5, but is F5 or other reload method avoidable?
Also index.html needs a <meta> or something to turn off browser cache, isn’t it?

Hi!
Are you shure about point 2, browser cache is taked into account, so user can see changes just pressing F5 (not ctrl+F5)?