UPDATE: this ticket covered a lot of ground, and some of this had been completed a long time ago, while work has not yet begin on other parts.
All of that work has either been completed already, or split into other tickets.
All that's left here is the discussion that started in this comment, about whether or not we can use an existing OOUI multi-select dropdown element in favor of rolling our own.
I updated this description to make that slightly more clear. Also check out this comment for the current state of affairs.
This ticket covers needed updates for the basic search bar in advance of the Depicts January launch, per conversations with @MarkTraceur and @Ramsey-WMF regarding media/file types and @Jdforrester-WMF and @Nirzar regarding OOUI tabbed navigation.
User story
As a… Commons user
When I… search for media files
I want to… apply search terms and requirements to ONLY images, or only videos, etc.
So that I can…. find a specific media/set of media which match my needs
Link to story
Dropdown filter options
Strikethrough, as this feedback has been split up into other tickets: T216536, T216538, T216540, T216541
After multiple conversations, here's what we think will be best in terms of grouping files by media type (according to CirrusSearch capabilities) for filtering:
Filter by type of media (for both Keyword and Depicts searching)
Images [SVG, PNG, JPEG, GIF (static & animated), TIFF, XCF]Audio [MP3, OGG (audio), WebM, FLAC, WAVE, MIDI]Documents [DjVu, PDF](this used to say "Text", but changed, per follow-up comment)Videos [WebM, OGG Theora (video), APNG]3d [STL]
Visual:
Tabbed navigation
Strikethrough, as this feedback has already been integrated into https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikibaseMediaInfo/+/441040
Currently, we've been using this design for tabbing between Keyword and Depicts search modes:
However, though the above version tested well, the styling is not supported by OOUI and we'd like to keep things consistent.
Here is the updated version:
And another example (showing what it looks like before anything's been typed yet):