Nice solution. I came across the same error using that package
Posts made by Nicholas
-
RE: How do I modify the output key in webpack config
-
RE: Detecting "platform is desktop" does not seem to work with Firefox or Edge on SSR with PWA client takeover
I have come across this bug too.
My layout drawer keeps closing whenever I enter the page on Firefox and Edge (I’m using a standard Quasar 1.0 SPA).
Works fine on Safari, Chrome. -
RE: [Bug] UMD q-list items (text colour and underline)
@s-molinari
Thanks for that Scott.
Yeah I figured the solution was simple, but I gathered that this fix could be added to the underlying Quasar CSS.
All good though -
[Bug] UMD q-list items (text colour and underline)
As continued from this thread: https://github.com/quasarframework/quasar/issues/2471
I’m trying out the UMD version of Quasar and I’m having problems with text colour and underline on q-items which use
tag="a"
Following fiddle shows the problem: https://jsfiddle.net/waugrryy/5907/
In case the link doesn’t work, this image shows the problem:
https://i.gyazo.com/a5c265d17ef83efb06c7a9cb882e7ebf.png -
RE: Datatable: Hide columns in mobile view?
@ssuess That’s right. I have got it working based on screen size, but like you mentioned, its either everywhere or nowhere. It is a working solution in my case though; but it would be a lot easier if we could use CSS classes to manipulate the table instead.
-
RE: Datatable: Hide columns in mobile view?
+1.
Can’t find any information in the docs yet. I’d like a class attribute in the columns array which lets us do something like:
class: ‘gt-sm hidden-sm’ etc -
RE: Quasar v0.17.7 & CLI v0.17.8 + Quasar Extras v2.0.5 are out!
Brilliant update as always, keep up the great work!
-
RE: Quasar & Quasar CLI v0.17.0 are out! SSR arrived.
@rstoenescu Thanks for quickly fixing that notify bug!
-
RE: Quasar & Quasar CLI v0.17.0 are out! SSR arrived.
What a brilliant release. Fixed a lot of small things I’ve had issues with.
Cheers! -
RE: Quasar & Quasar CLI v0.17 aka SSR - Developer Preview
What an amazing update! Brilliant stuff.
-
RE: My Portfolio :-)
@aryeh Thanks a lot
I’m going to try find a way to improve the speed, but as you mentioned, initial load is the biggest factor because it needs to load a lot of content into the cache. The files are stored on Amazon S3 in Sydney, Australia. I may have to store the files in multiple locations to improve that speed. -
RE: My Portfolio :-)
@shone Thank you for the feedback! Much appreciated and I’ll take it into consideration in the next iteration of changes I make.
There is no live demo of 1SPAN CMS at this point as the project is on-hold, but I’ll probably put up a live demo soon
-
RE: My Portfolio :-)
@joepstender Weird… I haven’t had any issues. May I ask what country you’re from? The site is hosted on AWS in Sydney, Australia.
-
My Portfolio :-)
Hello Quasar Community!
I’d like to take an opportunity to show off my new portfolio website which I’ve built using Quasar 0.16 and WordPress!
https://nickzuccarelli.com.au/
Feel free to take a look and let me know what you think!
-
RE: Platform detection and google chrome emulator
@paul said in Platform detection and google chrome emulator:
My Bad, need a hard Refresh. Probably platform is detected on app startup.
You’re right
You must reload the page for chrome dev tools to render the app using a specific platform. -
QTab dropdown menus
Hiya,
I’m wondering if we could possibly get support for QTab/QRouteTab dropdown menus in the future (working similar to the btn-dropdown except in tab-form).
-
RE: 0.15 with WordPress
@max I ended up figuring it out! There were only a few small changes I had to make to the quasar.conf file, otherwise it works perfectly!
-
0.15 with WordPress
Hey guys,
I’m wondering if I can get any help setting up Quasar with WordPress.
I am using the cli for installation.
I’ve successfully set up the framework inside of its own WordPress theme, but the only problem I’m having is that assets (such as images and fonts) cannot be found.
This is because they are trying to locate /img/, /fonts/ , whereas the actual files are located in /wp-content/themes/themename/fonts/.Is there any way I can modify the configuration quasar file to point the build to this location?
-
RE: 0.15 Notify with HTML
@mds1 Yikes! That’s certainly a nasty solution haha. I’ve decided to hold back from upgrading to 0.15 until these features and/or proper workarounds are documented (plus other bug fixes
)
-
RE: 0.15 Notify with HTML
@rstoenescu thanks for the feedback. But dialog doesn’t support HTML either anymore.
And as mentioned above, I need to use HTML in alerts for emphasis.