Hi, I have the exact same problem now… did you find a solution?

EDIT: try to add “fit” just where you defined the “ellipsis” class. It worked for me!

I tried to move the content in a page rather than in a q-dialog but I still have performance problem.

When I click the back button (basically a $router.push() to the list page) it takes several seconds before the page changes.

I can’t understand if my problem is related to Quasar or Vue… maybe they are not suitable for such amount of content?

Hello,

I have a q-dialog component with a custom component as content.

    <q-dialog full-height full-width persistent v-model="showEditDialog">
      <q-card class="full-height full-width">
        <q-card-section class="row">
          <div class="text-h6">Edit</div>
          <q-space />
          <q-btn icon="close" flat round dense v-close-popup />
        </q-card-section>

        <q-separator />

        <q-card-section style="height:calc(100% - 120px)" class="scroll">
          <CustomComponent ...></CustomComponent>
        </q-card-section>

        <q-separator />

        <q-card-actions align="right">
          <q-btn label="Save" color="positive" @click="save()" />
        </q-card-actions>
      </q-card>
    </q-dialog>

This custom component is a huge form to create a survey with a lot of questions and every question has many other input fields alongside with answers of course.

The dialog close button has the v-close-popup property. When I close the dialog it takes about 10 seconds before it to disappear.

I guess the problem is the amount of content… what I could try to speed up the closing of the dialog before moving my custom component in a page rather than in a q-dialog?

Thanks

Hello,

is it the expected behaviour that q-table column sorting go back to the first page when in second page or more?

If so, any chance to make it sorting in the current page?

Thanks

Yeah, I confirm! Very annoying!
@sibylle did you find a solution?

@mKomo you helped me, thanks!

Ok, after some days of curses and desire to destroy my computer, it turned out the problem is the Android version of the AVD.
26 doesn’t work but 27 and above do!

Computer technology … love… hate… love…

Hello,

I’m building an Android PWA on my brand new Ubuntu 20 but Remote Debugging on Chrome has changed (and this doc link https://quasar.dev/quasar-cli/developing-cordova-apps/troubleshooting-and-tips#Android-remote-debugging is now obsolete).

Now there’s this new “chrome://inspect/#devices” interface but I cannot see the network activity. Almost all panels are empty. The network panel has no submenu. Even the console panel is completely blank.

I’m using the command “quasar dev -m cordova -T android” (tried also quasar dev -m cordova -T android --debug).
My Chrome version is 83.0.4103.61 64 bit.
quasar-cli version is 1.8.6.

Building the iOS version on Mac with Safari has no problem.

Am I the only one facing this problem?

Thanks!

Well, somehow I managed to make quasar work with the emulator… maybe removing and recreating the avd did the trick… maybe reinstalling cordova package…
Anyway the emulator still doesn’t start automatically but it’s just a small annoyance.

For the sake of completeness I found this issue on cordova github: https://github.com/apache/cordova-android/issues/698
We are not alone…

Well, somehow I managed to make quasar work with the emulator… maybe removing and recreating the avd did the trick… maybe reinstalling cordova package…
Anyway the emulator still doesn’t start automatically but it’s just a small annoyance.

For the sake of completeness I found this issue on cordova github: https://github.com/apache/cordova-android/issues/698
We are not alone…