thanks for that

when a button has the disabled property applied the tooltip doesn’t show at all

So, in order to get that working without touching quasar, someone would have to rebuild the google fonts and the custom ones? Is that even possible the way quasar is setup (the way it reads fonts that is)?

Can you give me an example of how it would work in practice in quasar? for example, i need a custom icon on a tab,

<q-tab icon="my_custom_icon" route="/in" exact replace>
                In
              </q-tab>

How would i set this up? Can i use a png instead and if so how? I tried using an img inside q-tab but it just doesn’t work as well as the icon prop.

nice one, thanks.

Is there a simple example on how you invoke that minimized modal?

How do you go about rendering a component in a dialog? If that’s not possible, how do you form a bit more non standard modals?

I found out that the fastest way is the microsoft cordova-simulate plugin in compination with webpack --watch.
webpack --watch writes files in dist, and the simulate plugin lifts a server simulating most cordova plugins. This way it feels like developing on chrome instead which is fine for like the 90% of any simple mobile app.

I did have to comment out this line in quasar-common if (Platform.is.cordova && !Platform.within.iframe) { in order for this to work. @rstoenescu is taking care of it though which means it will make things even simpler since we will be able to declare the platform at build

Does anyone have any suggestions on the best way to develop cordova apps? At the moment my workflow is dead slow, as i have to do a webpack build (so that the files will end up in the dist folder) which takes forever and then a cordovar run which again takes forever.

So for every little change it takes like 2 minutes to test it.There must be something like live reload, right?

Is there a way to use local svg icons in addition to the default material ones?

So, the problem is in quasar.common.js here

else if (window._cordovaNative || document.location.href.indexOf('http') !== 0) {
    browser.cordova = true;
  }

Apparently, when in chrome extension document.location.href.indexOf('http') !== 0 is true, so browser.cordova becomes true and then it tries to load the cordova.js

Platform.is output

chrome : true,
cordova: true,
desktop: true
name: "chrome"

After some digging, i found out that the problem is that the app is being detected as cordova although it isn’t. What could be triggering the following code?

if(te.is.cordova&&!te.within.iframe){var e=document.createElement("script");return document.addEventListener("deviceready",t,!1),e.type="text/javascript",document.body.appendChild(e),void(e.src="cordova.js")}

I’m building a chrome extension, and all seems fine during development. When packing it though (npm run build) and loading the extension, i get a cordova.js net::ERR_FILE_NOT_FOUND

Opening the vendor.js i see a void(e.src="cordova.js") which begs the question why is cordova requested in the web build and why it works fine outside the chrome environment.

Any ideas?