@rstoenescu I think this may be a bug with the quasar cli and the sw-precache-webpack-plugin. I have a similar problem and started tracing through the quasar source code and found.

line of 401 of https://github.com/quasarframework/quasar-cli/blob/0eab359c1741f6d6304fcd5359b592c628b35128/lib/build/webpack-config.js
we can see that
stripPrefix: cfg.build.distDir + ‘/’

in theory the stripPrefix should remove the ‘dist/pwa-mat’, so it doesn’t end up in the service worker, but it doesn’t

I tried adding my own stripPrefix property to the ‘quasar.conf.js’, but obviosly that won’t help, because the q-cli is hard coding the stripPrefix based of the cfg.build.distDir

the docs state that the distDir should default to ‘Relative path to project root directory. Default is ‘dist/{ctx.modeName}-{ctx.themeName}’. Applies to all Modes except for Cordova.’ http://quasar-framework.org/guide/app-quasar.conf.js.html

line 225 of this file seems to prove this https://github.com/quasarframework/quasar-cli/blob/16df4efe6555e1a8c64c05357468bb72d57411c4/lib/quasar-config.js

HOWEVER the stripPrefix doesn’t seem to be working with the quasar defaults.

If I manually add ‘distDir: ‘dist/pwa-mat’’ to the build in quasar-config.js everything seems to work as expected.

I my case, i don’t really want to manually add the distDir to my config, because we are building for a couple different environments.

Curious if there is a way for users to navigate the q-select component using just the keyboard instead of mouse clicks? My users need to enter data very quickly and therefore are very keyboard centric. For example, they will tab between the various fields on a form and when they reach the “State” select box will type “f” for Florida or “aaa” for Arizona, then tab to the next field without ever using a mouse. The q-select is very nice and fancy, but I haven’t found a way to mimic the traditional keyboard usage of the html select.

Any ideas?

I really like using chips for with my q-select, but it misaligns my forms and makes things look “off”. Any tips to help with this?

Just curious if it possible in Quasar 1 for QDate with QInput to display formatting to something other than YYYY/MM/DD. My users prefer to see their dates in MM/DD/YYYY format.

If there isn’t something for Sublime there should be. Maybe I will look into doing it.

If there isn’t something for Sublime there should be. Maybe I will look into doing it.

When I use q-select inside of q-expansion-item, the options seem to be bound by the size of the q-expansion-item and they get cut off. Pretty much making the select unusable. Any workaround for this?

Here is an example in CodePen https://codepen.io/daveline/pen/BbwKOx

@eelke Perfect thanks!

I am thinking we may need to add a null/empty value to the options, so it can be “selected”

However I do have this same issue

@daveline oops my issue was caused by not using the hide-selected property.

I have a similar issue, except I can’t backspace all the data. Looking at the html source, it is putting my selected value in a span before the input. ???

@rstoenescu Specifically on the select it would be nice to be able to type a letter and have you “jump” to that letter in the select. Kinda like a traditional html select tag. https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_select

Just curious if it possible in Quasar 1 for QDate with QInput to display formatting to something other than YYYY/MM/DD. My users prefer to see their dates in MM/DD/YYYY format.

@rstoenescu What if I have a bunch of other things on the server? Including other PWAs? The PWA app needs a place of its own so it can play nice with others.

create a separate sub-domain?
different names for the various service workers?
other?

This did work in .15