Im trying to change the font size inside q-input textarea component. class inside q-input seems not working… I tried to change it in the scoped style by selecting the class as the following:
.q-input textarea{}
It seems not working as well!!
Any idea?!
Best posts made by amer1616
-
Changing Font size inside q-input textarea
Latest posts made by amer1616
-
RE: Quasar with Vue 3
I hope to rewrite the components in composition api. It opens new world of possibilities and I’m sure to save a lot of codes & resusable functionalities
-
RE: [Solved] PWA force refresh when new version released?
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 -
RE: fluid typography - SOLVED
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?
-
RE: v1 QSelect cant change value with object options
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!!
-
RE: [v1] Quasar v1.0.0-beta.12/13 released! Don't miss it.
@rstoenescu thank u. Now it is working well
-
RE: [v1] Quasar v1.0.0-beta.12/13 released! Don't miss it.
@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 commandquasar 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!! -
RE: [v1] Quasar v1.0.0-beta.12/13 released! Don't miss it.
@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" } }
-
RE: [v1] Quasar v1.0.0-beta.12/13 released! Don't miss it.
@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.
-
RE: [v1] Quasar v1.0.0-beta.12/13 released! Don't miss it.
@metalsadman really I tried many times to upgrade quasar package with
quasar upgrade --install
. but nothing changed. so I do it either byyarn upgrade
ornpm update
-
RE: [v1] Quasar v1.0.0-beta.12/13 released! Don't miss it.
@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?!!