Well just after I posted this question I figured how I can do this. One has to give a max-height to the .q-table__middle.scroll
https://codepen.io/turigeza/pen/pBZWmd

So I have not got a problem making a sticky header column in a normal html table but when I try to do the same to QTable it does not work.

Would somebody be so kind to show me what I am missing ?

https://codepen.io/turigeza/pen/VNBPKL
https://codepen.io/turigeza/pen/rbrzqM

@spyke113 Thank you for suggesting the computed property in your pen here:
https://codepen.io/spyke113/pen/bJEyEJ

So the solution is to use a computed property for the model with a getter and setter.
This is what I was after a simple select with a search box which uses key value pairs for its options.
https://codepen.io/turigeza/pen/rbpLRJ

IMO this is such a common use case it should be one of the examples in the docs. No?

Would somebody be able to point out what I am messing up. Or is this a bug? Basically I would expect never to see the value displayed in q-select. Yet when I load the page this is exactly what happens. One sees the value of the model instead of a label. In this case 'goog'.

Please see pen
https://codepen.io/turigeza/pen/QPObae?editors=1010

Any idea ? Thank you !

Btw all I am trying to achieve is how a native html select would work. I need to see labels displayed and values used for the model. I also need to be able to jump to the option when I type or filter in this case.

@mohanzeal They say you should use css position sticky. So there is no built in support as such in v1.
https://github.com/quasarframework/quasar/issues/2966

Very basic idea with a table I first played with.
https://codepen.io/turigeza/pen/QoBNjz

I have to solve this later in the week as well.

Done. Thank you !

@Marco
While others like myself expect it to behave as it does : )Or
ascending
descending
not ordered

For me this is the normal. Btw how would you clear the sorting (get to a not ordered state) if it was toggling just the two state ascending/descending ?
I would say use the custom sorting as you pointed out.

@rstoenescu

I want to know when ALL the files have finished. That is uploaded or failed.

As far as I can tell uploaded({ files, xhr }) fires after every single file upload has finished not when all of them.

So if I am uploading 10 files it will fire 10 times. And not once when all of them is finished. Also it does not fire when the upload fails. (There is @failed -> function(files, xhr) for that I know.)

@finish fired once. ( no ? ) And it fired after everything is finished. Ideal for me. Because that is all I need to know.

Thank you,

So uploader @finish was removed in v1.

What do I replace it with ? I mean I need to know of the uploader has finished either failed or succeeded.

@s-molinari My intentions were good . : ))