No More Posting New Topics!

incase you looking for v2 with vue3

const pickup = ref<QInput | null>(null);

<q-input class="full-width" required ref="pickup" type="text" dense label="Enter Pickup Location" v-model="form.pickup" /> let input = pickup.value.getNativeElement() as unknown as HTMLInputElement; return { pickup, .... }

@toymachiner62 said in Date util documentation doesn't make sense:

On this section https://quasar-framework.org/components/date-utils.html#Create it mentions that you can pass a third parameter, but there is nothing documented about what the second parameter is supposed to be. Can that be updated to be more clear?

I’m also looking for the syntax to add ‘true’ to get the UTC date.

Even if I use adjustedDate and put in true, I’m still getting my local timezone, not UTC:

const newDate = new Date(2017, 10, 2) const adjustedDate = date.adjustDate(newDate, { year: 2010, month: 2 }, true)

I’m using extractDate…

const extractedBeginDate = date.extractDate(this.begDate, 'YYYY-MM-DD')

Hello @gunturhakim ?

Now, to figure out why the marker png’s don’t work with Webpack.
net::ERR_INVALID_URL

Accounting tools can be of great assistance, so as totackle out different processes and tasks. In today’s post, we will be learning the procedure to access different accounting tools in QuickBooks desktop enterprise. Accounting tools can be a saviour in majority of cases.

To know more about accessing accounting tools in QuickBooks desktop enterprise, make sure to read this post till the end.

this may be late just incase use this https://github.com/diadal/firebase

The simplest way is giving a long pattern like:
{
mask: “###.###.###.###.###.###.###.###,##”,
reverse-fill-mask: true,
}

@damiendeville
This has been confusing me as well!
I also need an online database backend for Quasar and have been looking at Meteor. But there is really no information about that

“a) The commands to create the project do not mention neither meteor nor quasar”

Solved with this pcs of code:

console.log('%c Service worker is active.', 'color: magenta', registration); const updateManual = () => { registration.update().catch((er)=>console.error('Error on update worker', er)); }; setInterval(updateManual, 500); // 500ms works for me, but you may want to set it higher. },``` in case someone else need it.

declared as closed

@Hawkeye64 Like most technical questions in programming forums, this question can be answered in two ways:

Hey, what you are trying to do (called X ) is not the recommended way. So, do Y instead. (An example of XY Problem – https://xyproblem.info/) Ok, let’s assume you know what you are doing and you have your own reasons to do X instead of the recommended way of Y. Here is the easiest way to achieve that.

I believe your answer was case #1 above. And there are people who are looking for #2. As a core Quasar Team member, it would be wonderful to hear your answer to #2.

What I have found is the common way of preloading in Javascript (https://stackoverflow.com/q/3646036 – just (new Image()).src = url;) does the work here. Note that q-img often loads the image twice (Read more details in my answer here: https://github.com/quasarframework/quasar/issues/7053#issuecomment-771938111), but the second time it’s from the cache. So if you want to test it, make sure you have Disable cache in Chrome DevTools unchecked.

Additionally, I’ve found that adding basic and no-default-spinner to the q-img element can make it show up faster – from the API doc: https://quasar.dev/vue-components/img#qimg-api

I still see some lags, but that’s the best I could come up with.

For anybody has trouble showing the dropdown list on cordova app, the problem for me was the css. I solved with this instruction:

.pac-container {
z-index: 9999 !important;
}

For anybody has trouble showing the dropdown list on cordova app, the problem for me was the css. I solved with this instruction:

.pac-container {
z-index: 9999 !important;
}

@steve

devServer: { https: false, port: 8080, open: 'chrome' // opens browser window automatically },

For automatically opening Google Chrome

@sebag well, late to the party, but you could do something like…

actions: [ { icon: 'close', color: 'white', handler: () => {}, }, ],

and your css could be…

.q-notification__actions .q-btn__wrapper.col.row.q-anchor--skip { padding: 0px !important; font-size: 8px !important; } .q-notification__actions .q-btn__wrapper.col.row.q-anchor--skip i { position: absolute; top: -10px; font-weight: bold; }

@cata-orellana
https://github.com/quasarframework/quasar/discussions/9065

conseguiu resolver seu problema?

Just a note: Be sure the style is not scoped to your component.
In Electron this works:

<style> input[type="number"]::-webkit-outer-spin-button, input[type="number"]::-webkit-inner-spin-button { -webkit-appearance: none; margin: 0; } </style>

But, <style scoped>…</style> doesn’t.

Scoping the style appears to work in browsers, but failed for me in Electron.

@dsl101

I agree, you could create feature request in github:
https://github.com/quasarframework/quasar/issues

or open a new discussion about it on the new forum( this forum is dead):
https://github.com/quasarframework/quasar/discussions

@tlloyduk

I would ask this on the new forum where the Quasar team now gives support.

https://github.com/quasarframework/quasar/discussions