Here are the working svgs for 1 and 2. 2 seems to me to be the more promising of the two, but would need a few edits (like centering and a modified result screen) before it is ready to go.

Here are some more potential version drafts

I agree. Here are two versions with small changes that might begin to address that.

This is looking good!

Updated Findings

• WP users overwhelmingly use the defaults: content (article), everything (all namespaces), and multimedia (file), generally in that order.
• The other findings mostly still stand. The "percentages of total searches" from previous findings go down quite a lot since the default button options, which make up the large majority of searches, were included
• wikis that have the "topic" namespace (I checked de, es, fr) often remove it (not actionable, just interesting)

I think it would make the most sense then to use the Commons version for Wikimedia projects since that is what I understand to be the main use case.

Here is our current suggestion for the help text. Let us know what you think/what should be changed.

Just so I make sure I understand, the Exporter extension could export to any MediaWiki using the Importer extension?

@Addshore we were discussing this earlier. Is it problematic that this points to Commons? Should it be wiki-independent?

@Jakob_WMDE can you add a screenshot of what the current patch would look like?

I've been having some major struggles with the svg format today.

Some stuff I used/made

I've been looking through this data and have some insights.

Some notes:

Here are some mock-ups for a version 1 of this sequence.

I would add a little bit of space to show the separation and make it visually clearer.

@mpopov was it intentional to not include ns0, the article/main namespace in the results of the query?

When would you tab to the save button instead of pressing enter to save? (besides when there is a popup that makes it so you can't as in T96160)

This mostly seems to be working now. The language field disappears after you tab away from it, which isn't good, but you can definitely tab over to save in Chromium and Firefox at least.

@Volker_E, my understanding was that it was intended to denote distinct "units" in the search that could also have arbitrary punctuation in them.

Here are some quick mock-ups of what I'm talking about. Poke some holes in them please.

These images come from a blog post about design and accessibility.

I think that there is a lot of value in keeping 2 fields.

1. That was actually one of my working ideas when I was designing this. A lot of my earlier (and now very outdated) mockups had such an effect. Here is one of those with two different amounts of opacity over the lines.

This could be a pretty quick job if it hasn't been done already. My initial 2 ideas are the logo with a question mark or a magnifying glass. Here are 2 lazy, 10 second drafts. Would this be on the right track?

When a user has entered something that doesn't match a property, there should also be some indicator of the fact that it won't be accepted as input. Gmail does a red underline as if the word was misspelled for example.

My first suggestion was "Inflected Forms."

You probably already know, but just want to clarify that means either that color or that opacity. There was a discussion over which way was better to do it, so we decided to include both options.

Here is a quick mockup of what some elements/placings might look like.

Here is our initial suggestion for modified spacing around the revision slider when collapsed.

Current prototype

They're uploaded here!

Sweet, thanks!

@Jan_Dittrich @Charlie_WMDE I threw together a quick version of this. Please drop by the document and make edits and give feedback when you can to make sure it is meeting the goals and making sense.

Right now, when you add ist ein there is an extra "duplicate" entry that could be potentially confusing and isn't present on production. Is this being used for something/can it be removed?

@WMDE-Fisch Should I upload these to commons beta feature icons category or does this happen automatically at some point?

@Lea_WMDE can I close this?

This bug is present in the current deployed revision slider as well.

To clarify, this bug is present in the current deployed revision slider as well.

See bugs

Here they are without the drop shadow and without the extra lines bug.

I had a quick look. Looking pretty cool!

Here are minified versions of v6 along with png previews. Still open to feedback, but otherwise consider these final.