Well in this case yeah. The simulator is Quasar App, which needs to be an app on its own. People install in Google Play Store, need to have a feel of the framework. When on a documentation website, the examples need to teach a certain aspect but in a gradually manner. The simulator UI in this case would be a too complex example when starting to learn about FABs (too many features at once in an example that should focus on FABs only).
Makes sense. Thank you.
I already passed this on to the developers here. If they go to analyze the Ionic site, the same thing happens.
Thanks! Turned out that my issue is a different one. In an attempt to avoid unnecessary DIVs I’ve added both layout-view and layout-padding to the same DIV. Turns out that this isn’t a good idea. Moved layout-padding into a separate DIV, scrollbar moved nicely to the right.
Using the name property has no place in talking about how to require/register a component because it doesn’t affect it in any way. This means however you can use and there’s no reason or recommendation not to. It’s just out of the scope of custom component discussion.
Some more things worth mentioning. I’ll just copy paste my comment on the latest Quasar starter kit / template:
* NOTE! VueRouter "history" mode DOESN'T works for Cordova builds,
* it is only to be used only for websites.
* If you decide to go with "history" mode, please also open /config/index.js
* and set "build.publicPath" to something other than an empty string.
* Example: '/' instead of current ''
* If switching back to default "hash" mode, don't forget to set the
* build publicPath back to '' so Cordova builds work again.
Also, changing the “publicPath” should be carefully considered as it impacts the way you reference static assets.