@rstoenescu
Ok but what about Qinput type=“datetime”? Is it possible in 1.0?

I also struggled with many components inside QTable. I replaced them using native html with quasar css:

<button tabindex=“0” type=“button” class=“q-btn inline relative-position q-btn-item non-selectable q-btn-rectangle q-focusable q-hoverable bg-white text-black”><div class=“q-focus-helper”></div><div class=“q-btn-inner row col items-center justify-center”><div>Standard</div></div></button>

This is not good long term solution but I agree that we need some functional components built in into framework - for exapmle: QBtnSimple, QIconSimple etc… This way we can avoid that future change inside framework css will break my native button styled using quasar css. I will create feature request for that using Github. Not everyone knows at the beginning why some components work so slowly using sub components.

Thank you very much !!!
My mistake was to use the navigation slot instead of the title slot in q-tab.

Hi,
I am trying to figure out how to make nested tab panes like in the following example:
http://reactcommunity.org/react-tabs/

Is it possible in quasar framework?

Awesome !!!. Thank you.

Awesome !!! Thank you.

It can be related with this issue:
https://github.com/vuejs/vue/issues/8507

I have the same issues with QDataTable. It seems like QDataTable slows down my web browsers after a few cycles of pagination and filter actions.

https://github.com/quasarframework/quasar/issues/2375

Hi,
How to style opened QCollapsible item? There is no css class applied to the opened item.
When I set popup prop in the QCollapsible component then q-collapsible-opened class is present but I don’t want to QCollapsible behave like popup . I believe that q-collapsible-opened class should be applied to regular items not only with popup prop. Am I missing something?