After painstakingly examining every change that resulted from an npm update, I tracked it down to a newer version of vuex-persist that was installed a couple of days ago. Why there was no warning/error/debug message of any kind is beyond me, but I am happy it is fixed.

when starting up my quasar dev environment this morning, my browser opens on a white screen of death. There are no console or other errors, just a blank screen being served up. I have tried rebuilding my node_modules folder, but no change. Any suggestions for how to debug this? With no error messages, it is very difficult to know where the problem is.

In case it helps someone else, I have found a way to keep my translation files separate on the backend but combine them for use in i18n as @s-molinari describes in his article. I simply add new files and then combine them before export in the i18n/index.js file, like so:

import enUS from './en-us/index.json'
import es from './es/index.json'
import ar from './ar/index.json'
import enUSstrings from './en-us/strings.json'
import esstrings from './es/strings.json'
import arstrings from './ar/strings.json'

const enUSCombined = Object.assign({}, enUS, enUSstrings)
const esCombined = Object.assign({}, es, esstrings)
const arCombined = Object.assign({}, ar, arstrings)

export default {
  'en-us': enUSCombined,
  'es': esCombined,
  'ar': arCombined
}

And voila! Now I can keep the actual translations modular while still using them in language switching anywhere in my app.

The Vue CLI has a really great GUI as part of it (https://www.codementor.io/jalasem/the-amazing-vue-cli-gui-l9hf48vjk), I was wondering if quasar has something similar or planned?

See below for a raging discussion on proposed changes to Vue:

https://news.ycombinator.com/item?id=20237568

And here is a direct link to the RFC:

https://github.com/vuejs/rfcs/blob/function-apis/active-rfcs/0000-function-api.md

omg, that fixes it!! Just adding no-focus to the menu! You are the best, thanks!!

I am, but that does not solve the problem of wanting to type more characters after. It only introduces a delay in the time before the menu shows, it does not leave input control where it should be (in the search input box). On desktop, programatically returning focus to the input works fine.

As mentioned elsewhere, I have a q-input search component that is triggering a q-menu to show while the user is typing their search (it triggers an api call to return search suggestions). In order not to lose focus on the input while the user is typing, I am also calling this method:

searchFocus () { this.$refs.searchfield.focus() }

This works on desktop and seems to also work on Android, but on iOS, focus is not returned to the input, or at least the keyboard is being hidden which amounts to the same thing: the user is constantly required to click in the input again to continue typing their search. Does anyone have any suggestions for a solution that will also work on iOS? Thanks!

omg, thanks! That is way easier than the contortions I had to go through!

Ok, I think I figured this out. I had to attach a watcher to the search and run the debounce function there. @input was the wrong place apparently.