If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.
No one has replied
After using @load for the scroll-element and adding a nextTick it seems to work as should. See this stackoverflow-issue .
@metalsadman Great! Thanks!
Shit… I’ve just realized, there’s an inconsistency:
For average q-btn is size, but for q-btn with fab property is padding…
@metalsadman I think this could mislead other as it happened to me. I recommend you to consider this improvement
@rstoenescu said in [15.1] Lazy loading of components:
The docs indeed explain code splitting and lazy-loading but don’t mention how the components in quasar.conf.js fit into this picture.
we updated the board… maybe something helped that 😉
I use Vee Validate, it work fine
that set is nice!
Ah, found an example in the quasar template:
Ah… it is in the documentation (gloops):
Used this and everything is working brilliantly:
<q-layout ref=“layout” :left-breakpoint=0>
Seems like trouble for mapbox-gl. Can you set some breakpoints and see where exactly it fails?
The following will prevents the refresh
Ok, thanks for the feedback @MusicForMellons! It is definitely pretty spotty based on the browser implementation.
I know this was ages ago, but this will help others too (and lets face it, the docs search engine needs some help too):
Yeah, setting these and adding to class works. Via css setting color to .item > i.item-primary also works. My problem was more of a ‘not working hot-reload thingy’ it seems. Thanks.