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.
Aah, I like you are careful at details! The “scroll” CSS class only applies some CSS tweaks to make scrolling smooth on ALL platforms. But it doesn’t make the container scrollable. You have to add some additional CSS like overflow-y: auto besides setting that height and it will work.
EDIT: I’m talking wrong. scroll also adds overflow CSS to your container. So it should work as is!
Every cent counts, unfortunately. I’m not in a good financial situation anymore. Invested all my money so I could work full time for the framework for a year and a few months, and bills keep piling up 😞
Anyway, thank you for even thinking about it!