there is a great resources about this topic
https://deanhume.com/displaying-a-new-version-available-progressive-web-app/
https://stackoverflow.com/questions/52221805/any-way-yet-to-auto-update-or-just-clear-the-cache-on-a-pwa-on-ios

Awesome… we need more guides from css guru I highly suggest putting the valuable guides about the design & any tricks in special section or blog. What do u think?

of course, will not change the value. cuz :options is used for values inside an array. not for objects inside an array. you need to make computed prop. to iterate over the objects inside ngstates , then pick up name prop from it!!

@rstoenescu thank u. Now it is working well

@rstoenescu quasar info output showing the latest versions of @quasar/cli3, @quasar/app beta13, and quasar beta13.
Cuz I updated all that via yarn upgrade. But before that the command quasar update --i output showing the same --all papckages are up to date. And when I check package.json dependencies, no versions have been updated, even quasar info, not showing any updated versions!!

@rstoenescu
Quasar CLI · Gathering information...! All Quasar packages are up to date.

{
  "name": "quasar-app",
  "version": "0.0.1",
  "description": "A Quasar Framework app",
  "productName": "Quasar App",
  "cordovaId": "n",
  "author": "Mr <mr>",
  "private": true,
  "scripts": {
    "lint": "eslint --ext .js,.vue src",
    "test": "echo \"No test specified\" && exit 0",
    "dev": "quasar dev",
    "build": "quasar build",
  },
  "dependencies": {
    "@quasar/extras": "^1.1.0",
    "axios": "^0.18.0",
    "quasar": "^1.0.0-beta.11",
  },
  "devDependencies": {
    "@quasar/app": "^1.0.0-beta.12",
    "@vue/eslint-config-standard": "^4.0.0",
    "babel-eslint": "^10.0.1",
    "eslint": "^5.15.0",
    "eslint-loader": "^2.1.1",
    "eslint-plugin-vue": "^5.0.0",
    "strip-ansi": "=3.0.1"
  },
  "engines": {
    "node": ">= 8.9.0",
    "npm": ">= 5.6.0",
    "yarn": ">= 1.6.0"
  },
  "browserslist": [
    "> 1%",
    "last 2 versions",
    "not ie <= 10"
  ],
  "resolutions": {
    "ajv": "6.8.1"
  }
}

@rstoenescu yes im running the latest quasar-cli 3 globally. Actually there is no error i see. Only I get info that all quasar package is up-to-date. There is no yarn process executed at that time. Im running Windows 10 with the latest yarn & npm. I didnt change anything in project folder.

@metalsadman really I tried many times to upgrade quasar package withquasar upgrade --install . but nothing changed. so I do it either by yarn upgrade or npm update

@rstoenescu Thank u. I’ve already used it for that but it needs some workarounds. By the way, have u noticed that if use img svg in QIcon, the color prop not working anymore. u have to style svg either in svg file or in css?!!

Awesome… images as icons really cool feature!! great as usual
One suggestion regarding QInput & QSelect. I hope to extract the autocomplete feature out to be independent plugin. so it can be used for both QInput or QSelect