CLOSE on select is redundant

[murbanowicz]

It is redundant and really useless.
To prove my word, look at other ui libs - you will not find it anywhere in any respected library. It even looks strange.

[rstoenescu]

The point of a framework is to offer components as generic as possible with as many features as possible. There may be cases when the developer wants to programmatically open the select popover. The argument that X other framework doesn't do this is not valid. Quasar is better than other frameworks. Please reopen with a solid argumentation.

[murbanowicz]

You're right. Then, there should be optional parameter
close='false' to disable it or enable - depends which one will be default.
Then Q will be really better than others! :)

[rstoenescu]

You've got disable Boolean property. Case closed. Q wins :)

[murbanowicz]

Not that easy! :)
I would really like to be able to not show CLOSE button on the top of options of multiselect ( type='checkbox.
I hope you get what I mean?
https://snag.gy/aOG3Zx.jpg

[rstoenescu]

Aha. You are referring to something else. Ok, will add a property. Do you care to make a PR? It's easy.

EDIT: Actually scratch that. I got a nice idea and will implement it in next Q. Anyway, that "close" button currently has its purpose. It doesn't forces the user to find an area with no click/tap events attached so he/she can close that popup. When on a narrow screen like a mobile phone that can be a small issue ;)

[murbanowicz]

Agree - should be shown on small screens as default, but on larger screens we need at least choice :)