QSelect taking all the height available in desktop when there are too many items in options

[dev-rfc]

What happened?

After upgrading from 2.12.0 to 2.12.2, the QSelect was affected, it currently fills all the space on the screen when opening and having too many items in options.

What did you expect to happen?

It should open and retrains it from occupying all the space on screen

Reproduction URL

https://codepen.io/renan-cavalieri/pen/rNQJxbp

How to reproduce?

1. Open the reproduction link on desktop
2. Open the QSelect component.
3. The issue should be visible, like in the screenshots.
4. If you need to compare to the previous behavior, check this link instead: https://codepen.io/renan-cavalieri/pen/KKrQVLW

Flavour

Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)

Areas

Components (quasar)

Platforms/Browsers

Firefox, Chrome

Quasar info output

There is no need, it's reproductible even in browser using UMD.

Relevant log output

No response

Additional context

No response

[binarytide]

possibly consider options-max-height as a param?

[dev-rfc]

could be, but that's not the expected behavior, as it's probably a regression that happened between 2.12.0 and 2.12.2.

[metalsadman]

I think this change did it back in 2.12.1 c9e43fa#diff-d486fe7e47b9fce07ab2252caf361429f339596767385dfdd8b53da0c72150b6R174 which was to fix (#11247), so even if you set popup-content-style="max-height: 65vh;" it will get overridden by 100vh or with the computed maxHeight when the engine recalculates.
https://codepen.io/metalsadman/pen/KKbVqVZ?editors=1010
default max-height per qmenu's css is 65vh
q v2.12.1

q v2.12.0

[SeverinSenn]

Just out of curiosity, did anyone find a solution to this problem?

[stijnelskens]

Any solutions for this? I'd like to keep a max-height without it gets overwritten.
As an fixed height is no solution for this..

[stijnelskens]

A possible workaround is adding popup-content-class="max-height-dropdown" and define the class with max-height: 40vh !important;. As this doesn't get overwritten. So this is a temporary solution..

@SeverinSenn

[rstoenescu]

Fix will be available in Quasar v2.17.0