In quasar.conf.js

    pwa: {
      manifest: {
        display: 'standalone',
        orientation: 'landscape',

All other options are listed here: https://developer.mozilla.org/en-US/docs/Web/Manifest#orientation

I’m creating a html5 game using Phaser 3 game engine and I want to use Vue and Quasar advantages in it.
The problem is that in fullscreen mode Quasar doesn’t work in all major browsers except Firefox and UC Browser

Here’s the code: https://codepen.io/rusia_/pen/JzrVpm

Before displaying Quasar dialog I have to hide Phaser canvas with style="display: none;" and then after the dialog is closed the canvas restores.
If you click “Go fullscreen” and then “Open Quasar” you will see a QDialog.
All browsers display it properly, but the button “Return to Phaser” works only in Firefox (both desktop and mobile) and UC Browser (mobile). I didn’t test in Safari because I don’t have an iPhone.
In all other browsers to make it work you have to exit fullscreen by pressing Esc or F11 (or Back button on mobile)
I tested in all major browsers on Android and Windows (except Edge).

What am I doing wrong? Or is it a Quasar bug or Phaser bug or browser bug or whatever?

@elias-p said in Can't get rid of vue-router:

Is it a necessary evil or I miss something?

It’s no evil at all. Even if you don’t use router (that is you use only one route for the whole app) I don’t think it will affect anything (app speed, production package size etc.) So just don’t delete the router directory.

Your example looks cool!
However QBtnToggle is essentially a radio input but I need a checkbox style on/off boolean switch. That’s why I decided to use plain html input tag instead of Quasar element.

Yes, Razvan said that in order for an accurate Material Design on checkboxes, this feature had to be dropped, and suggested using QToggle with icons.
I tried QToggle and it worked but the look of it didn’t satisfy me.
So I finally decided to create a workaround.
I used plain html <input type="checkbox"/> and styled it with FontAwesome icons as shown in this codepen https://codepen.io/imohkay/pen/wyxuB
Now it looks and works just like q-checkbox with custom icons in quasar v0.17
Anyway, thanks for you help, it is much appreciated!

Thanks for your response.
I created an issue linking to this topic.
To create a custom toggle button component is a good idea, I’ll consider this. I also thought of using some css trick like that: https://codepen.io/imohkay/pen/wyxuB
But, of course, I’d prefer this feature to be re-enabled in quasar. That would be the best option
By the way, do you have any idea why it was dropped? Nobody used it? Or any other reason?

I’m building something like a multi-track music editor. I use check-boxes with custom icons for triggering mute and solo states for tracks.
In v0.17 it looked nice:

Now in v1.beta it’s just horrible:

Of course, I believe it’s possible to create a workaround for this using q-btn instead of q-checkbox. But it would be just a workaround with a lot of extra unnecessary code. With checkboxes it’s a very short and comfortable code:

<div v-for="(track, index) in tracks" :key="index">
  <div>
    <q-checkbox v-model="trackUnmuted[index]" checked-icon="volume_mute" unchecked-icon="volume_off" @input="mute(index, $event)"/>
  </div>
  <div>
    <q-checkbox v-model="trackSolo[index]" checked-icon="strikethrough_s" unchecked-icon="strikethrough_s" @input="solo(index, $event)"/>
  </div>
</div>

I really have no idea why you decided to drop this feature. It is very useful and convenient. So if possible please re-enable it again.

I can see that in v1.beta there is no support anymore for q-checkbox checked-icon and unchecked-icon props as it was in v0.17
Are they removed forever?
This feature is indispensable for my app. Can you suggest some workaround?

@ben-hayat This command will check the registry to see if any (or, specific) installed packages are currently outdated.
npm-outdated

@labs20 first npm install -g npm-check-updates
then ncu -a
and npm i