It seems that I am implementing the router guards the wrong way. After correcting the code, the router guards now detects changes in URL even if the uses the back button.

@metalsadman Yup I did. But it doesn’t fit with my use case since it can’t determine what is the next route when the user clicked the back button. Router guards only handle the beforeEach and afterEach, but it can’t handle when the user clicked the back button based on my tests.

Good day. Is there any way to intercept/listen on the back button of the browser/phone? I would like to determine the route the user will be directed when the back button is clicked/pressed. For example in my situation, when the user clicks the back button simultaneously for a couple of times, the user is directed to the login page which is the app’s previous window(s). I would like to retain the functionality that the user can go back to the previous page but prevent it from visiting the login page when the user is already logged in.

Good day. I tried playing with QPopupEdit component in QDataTable and found out that it occupies the space of QDataTable if you type long texts on it. Is this an expected behavior? I think it would be better if the QPopupEdit is placed on a different z-index/layer or the QPopupEdit should not expand if a long text is typed without putting some CSS hacks. Here are some screenshots I’ve took. Thanks!

Try adding the replace directive as described here: https://quasar-framework.org/components/handling-back-button.html#Quirks
I’ve got the same problem too and the that directive fixed it.

Solved. It seems that the problem is on the version of the Android OS I’m using in the emulator. Currently I’m using Android 4.4 (Kitkat) and when I tried using Android 5 (Lollipop) as suggested by Razvan because Android less than 5 seems to use old web view, it worked. XD

Good day. I’ve started testing out Cordova in Quasar and can’t figure out since yesterday what might caused to display a blank page when app is run on the emulator. I haven’t tried installing the app on a real device since I don’t have one currently. I’ve carefully read the instructions on the Developing Mobile Apps section of Quasar Framework site and researched for similar problems but to no avail. The app is working when deployed on Web and as an Electron app though. This is the result of my trials:

I’ve never tried using QDatetime with seconds, but if it only allow those values, either you submit a feature request on the Quasar’s Github repo or you can create a custom component. Just want to share my mod QDatetime using QDatePicker and QModal -> https://imgur.com/a/zL0QOTk