@benoitranque I used it in QLayout like in 0.14 and it didn’t work. I didn’t notice that in 0.15 the reveal property moved to QLayoutHeader/QLayoutFooter as @cheebhodh mentioned. Now it works. Thanks @cheebhodh !

I added a QUploader to my component. It works okay. But when I press the upload button I get this message in console:

[Vue warn]: Unknown custom element: <q-spinner-undefined> - did you register the component correctly? For recursive components, make sure to provide the "name" option.

found in

---> <QSpinner>
       <QInputFrame>
         <QUploader>
           <Component> at resources\assets\js\components\Component.vue
             <Root>

File is uploaded properly, everything is correct except for this ugly warning in console.

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?

@michael123, Yes, I found a solution. Though I’d rather say I found a workaround not a solution. I’ll give you more details later. To be honest I already forgot how exactly I solved this))

I didn’t say that Quasar’s fullscreen api didn’t work, it works well. I only said that in this particular case when Quasar is combined with Phaser there were some problems in major browsers except Firefox.

When phaser is “inside” quasar in html/css terms (not javascript) there were major problems. I mean when you put <div id="phaser"></div> inside <div id="q-app"></div> so that it looks like

<div id="q-app">
    <div id="phaser"></div>
</div>

then you have problems.

But if you isolate them:

<div id="phaser"></div>
<div id="q-app"></div>

then they can live together.

I believe that generally it’s only html/css problem. Despite all my years of coding experience I still can’t grok css))

But in terms of javascript quasar, vue and phaser co-exist perfectly. No conflicts, no problems ever.

@AgriTheory I set up Cordova in its default way without Quasar. And then added Quasar to the app’s default html page as UMD. This was the only way I could use all Cordova plugins.

@jeffatpf You can manually change them to latest versions in package.json
I do so and it doesn’t harm my projects.

I solved this by adding this code when putting Quasar div to foreground:

document.getElementById('q-app')[this.phaser.scale.fullscreen.request]().then(() => {}, () => {})

https://codepen.io/rusia_/full/EBEKPE

However I noticed that in current version of Chrome that problems doesn’t exist anymore.

@michael123, Yes, I found a solution. Though I’d rather say I found a workaround not a solution. I’ll give you more details later. To be honest I already forgot how exactly I solved this))

I didn’t say that Quasar’s fullscreen api didn’t work, it works well. I only said that in this particular case when Quasar is combined with Phaser there were some problems in major browsers except Firefox.

When phaser is “inside” quasar in html/css terms (not javascript) there were major problems. I mean when you put <div id="phaser"></div> inside <div id="q-app"></div> so that it looks like

<div id="q-app">
    <div id="phaser"></div>
</div>

then you have problems.

But if you isolate them:

<div id="phaser"></div>
<div id="q-app"></div>

then they can live together.

I believe that generally it’s only html/css problem. Despite all my years of coding experience I still can’t grok css))

But in terms of javascript quasar, vue and phaser co-exist perfectly. No conflicts, no problems ever.

How can I use this Cordova plugin in Quasar?
https://github.com/mauron85/cordova-plugin-background-geolocation

From Quasar docs I figured out how to use Cordova official geolocation plugin https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-geolocation/index.html
But could not understand how to use mauron85 plugin. Any ideas?

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!