-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Search device list by display size #613
Comments
Hey @romeo-folie π, Thank you for opening an issue. We will get back to you as soon as we can. Have you seen our Open Collective page? Please consider contributing financially to our project. This will help us involve more contributors and get to issues like yours faster. https://opencollective.com/responsively
|
@jjavierdguezas "Manage Devces > Active Devices, Inactive Devices with search...(text input)" If a number is entered on that input, should I show the device of the relevant size? Should I find a device that's close to number? Thanks. |
Hi @kiwan97 and also include the width and height in the filter here (as strings), I don't think it is necessary to do something more complicated here what do you think @manojVivek |
I am thinking about this again, and maybe @romeo-folie was talking about the quick filters? π€ |
Hi. No, I wasn't talking about the quick filters. I was referring to the search input above the list of inactive devices. The way I imagine it working is that a user enters a dimension value for the device they want and the list of devices is filtered to only show devices with that width or height. Say I enter 1000, any device with dimensions 1000 x ??? or ??? x 1000 should be included in the filtered list. |
π Feature Request
π Description
The device list should be searchable by display size.
β¨ Describe the solution you'd like
It would be extremely convenient if a user could also search the list of devices by display size. For instance, I'd expect to see the iPad Pro when I input "1024 x"
The text was updated successfully, but these errors were encountered: