I had in v0.17 a transparent drawer and wasn’t able to recreate this in v1.
Normal things, like dialogs I do with something like this.
style=“background: rgba(90, 60, 90, 0.6) !important;” inline color=“white” text-color=“primary”>
If I try this on btn dropdown or drawer it just get “milky”. Looks like there are some solid backgrounds I can’t address.
Is there a solution?
Thanks for your example! Helped me a lot, also the codepen was very helpful.
As not that appreciated workaround I tried without success:
<q-td slot=“body-cell-color1” slot-scope=“props” :props=“props” :color=“props.value”>
also
<q-badge color=“props.value”>{{ props.value }}</q-badge>
did not led to the desired result. What colorinformation is needed, if not something like #46ff3c?
What would be the best approach to colorize specific table data. The table itself and its structure is generated.
E.g. I do have some table data, containing only color information; also for positive negative numbers this would be great.
Valid solutions would be to colorize the td background - but than again, the information is only in the data and varies from field to field.
I also can imagine to put some kind of badge into it, but as far as I know, the information in the table can’t be components. This also makes absolute sense!
So which options are left?
I don’t want to colorize the structure itself, even if this would be great. But I don’t wand to color every second column, row or alike. I really need this specific for the field.
Will try the bg image approach. I think this could be my solution. Will report back.
One specific question / feature request I do have: How would I do it that one section is shown with mouse out and “effects out” - while another section “effects in” with mouse over.
Would be great for labels as in titles and descriptions.
Maybe “inversed transition” is the key word here?
And yes, you can have a look in the source. As being fullstack including devops myself, I do have a wide range of tech and information need to know. The better the documentation, the less hazzle do people like me have. And I bet, I am not the only one not having 10 years frontend experience or specialization in node / vue / css and companion techs. 
As implicit in using your flashcards, I think they are great.
May I ask for an improvement in the example section? It would be great to see the source code of the different examples, so I can easier work with them. Reverse engineering is so cumbersome ;).
( https://quasarframework.github.io/app-extension-qflashcard/demo/dist/spa/#/ )
Even for your ONE example, I need to figure out the style myself. Your work IS great, your documentation isn’t. But in adoption of tech, documentation is a big factor. And from a creators perspective, everything is known, everything is straight forward - if it wasn’t the creator wouldn’t have done it this way. Implicit knowledge is the keyword here.
Talking specifically of your extensions: not being documented at least in a intermediate manner, it hurts your great results. The best tool won’t be used if only few people are able to understand how it works and have to be used.
What would be the responsive and working way to fit an image into the flashcard?
It mostly ignores the image style and is only shown partly - i some places. Seems to dependof elements outside of it. Any tipps?
Also img works, q-img not.
Is there some functionality within quasar or vue to get the sizfe of an element, analog to $q.screen.width for screen?
Example: If a screen contains a container I would like to have its size in pixels. How would I do this?
thx! your support is great.
Is there a keep alive function like in v.017? Or should this be solved some other way? (If so, a hint would be great)
In the documentation as far as the search goes (field & input) there is :rules and :validate described.
I would expect only one of it.
Currently I encounter some unexpected behavior with date/time picker within input, while I try to reset the referenced input field. Doesn’t work for me. After resetting the input vars to null or ‘’, the error stays.
This said: a section of documentation for the quasar internal validation would be great.
Can’t compile anymore. Nothing else changed, just upgraded, also removed all extension.
https://github.com/quasarframework/quasar/issues/3898
@Cobeland
I develop for a productive thing to be in the open. I also value versions less than impressions. So I don’t understand why a RC or GA is that important. Only reason to care about numbers is compliance. And compliance is no technical spec ;).
In fact, I develop since 0.x. The changes to 1.x - I admit - took more time than expected. I could have had waited for the migration doc but I decided otherwise.
So until my project is live, I’ll migrate Quasar-Framework ASAP and I don’t have had issues with it, since… I think 0.13.
Changes are always in software, may it from 2.3 to 2.3.2 or to 2.4 or from 0.9. As said, it is more or less a compliance thing aka mind trick. Every upgrade from every version can break or change things. And this far, Quasar-Framework is pretty stable for me.
And yes, ETA questions do annoy me ;).
I was also looking into this forum tech. First impression was… oh, another simplified forum… but after registration and the first usage I have to admit - it is a really good choice! Sadly I do have other topics on my list first - but on longterm some kind of integration would be awesome. Even if I assume, theres not much relation and it is more a topic for the specific app someone wants and the integration will be more or less “quasar framework agnostic”. But still, this is just guessing at the current state of information - at least from my side.
If I may add: your fast response is VERY helpful, as it helps your users not wasting time in such topics. And I don’t take this for granted. With your replies to my - misplaced - reports you saved me some hours today. And I’m sure others feel alike.
@rstoenescu
Tanks for your response. I understood: bugs and or feature related things should be addressed on github.
I’ll do so for future topics of this kind. Sorry for bothering here and thanks for the quick response and your understanding. This won’t be forgotten. 
In v0.17 it was possible to set the label-value option and it was an option with great use.
In v1 I couldn’t find anything alike.
I want to customize the native slider label, e.g. text instead of number.
What would the way in v1 to do this? If there is none, I do have a feature request.
quasar beta10/ app11
I do have a component which is within a q-dialog with a q-stepper.
Within this stepper I do have some fields, including one q-select with 10 options.
The q-select option list is shown “under” the stepper, so scrolling is needed.
Especially on small (mobile) screens, it makes some options unselectable because many of them may be hidden under the stepper title.
It seems to be a bit better if it is opened to bottom, sometimes it opens to upper space and hides half of the option.
Ideally it would open above of everything, so the user can see all the options.
With 0.17 the full screen dialog/modal(?) was great for smaller screens - as far as I remember, I hadn’t such problem back then.