@reks But when I try to see output in IE it is inivisble… Does that mean that only the dialog is not working/visible in IE? Or does it mean that the entire page/app shows as a white empty screen in IE.

@jainsuneet Does your code work as expected in the browser in SPA mode? Documentation states that it listens for key enter event but on mobile I am not sure how it will trigger. I don’t read that explicitly in the q-select documentation for @new-value … What I want is that when someone enters new value in q-select and go to next input the @new-value should trigger but this is not happening. Is this really what you want? Because I interpreted this as follows: If the 'next' input component gets focus, check if the the q-select has a new value and then do_something/fire an event.

@donsherman Just as a side note: testing for the validity of an email address is almost impossible to do correct. This video explains why( surprised me too btw ): https://www.youtube.com/watch?v=xxX81WmXjPg

@kris-erickson said in Add initial page to history in vue-router...: this is going to be a cordova Aoo so the back button on the device should work rather than having an html back button This is only valid for Android app’s made with Cordova not IOS apps( made with Cordova). Does this pushing routes and going back work as desired in SPA mode?( with the browser back button)?

@manubi You could try to change the component import strategy in quasar.conf file: Possible values for "all": 'auto' - Auto-import needed Quasar components & directives false - Manually specify what to import true - Import everything from Quasar First try ‘true’ strategy: framework: { // 'auto' replaced with true all: true ... If that does not work you could try to manually define all the used components: framework: { all: false, components: [ 'QLayout', 'QHeader', 'QPage', ect...] ...

@happymax yes you can see this previous thread ( second post) : https://forum.quasar-framework.org/topic/6927/vuex-getter-undefined/2

Wrap the component with Q-Field. https://quasar.dev/vue-components/field Scott

@manubi I would say, via making a new quasar CLI project and port your code, follow the docs everything about quasar CLI, boot filea, quasar.conf.js file which is similar to your vue.conf.js and etc… About quasar v2 using Vue 3, it’s still in the works. https://forum.quasar-framework.org/topic/6960/quasar-with-vue-3

@walfin thanks!

@PS did you manage to change it as I am having the same problem?

I am still getting the same error. Installing quasar ext add @quasar/testing throws an error “ext unknown”

Any news to this error/warning?

You are on the right track with this.$emit(). You need to create methods that fire the this.$emit() method so you can “pass” information up to the parent. In other words, instead of inline methods, create methods which will do the communicating up to the parent component with this.$emit(). Those emits (as you build them) become the events available to use on the parent. Props down - events up. https://www.vuemastery.com/courses/intro-to-vue-js/communicating-events/ Scott

Yes, @Hawkeye64

@Hawkeye64 I was wondering if there was a way to start loading the images immediately after first paint (in the background). Currently the first opening of my menu sidebar is lagging as it only starts loading the images when the menu is opened. I’m currently resorting to using img instead of q-img and putting in invisible imgs elsewhere on the page to force the images to load.

@dobbel Yeah I had been debugging my apps using chrome previously, but I was wondering if I could do so directly from within VS Code instead.

+1 for solving this