I second what @Lydia_Pintscher said. basically this

I think @waldyrious captured most of the points we identified.

@abian That's a really good idea. I'm petty sure I don't have any interface rights. Is there a way to address all of them without having to ping the lot? Otherwise I could ask @Ladsgroup

Hey @abian, I'm not aware of any such rights. @Lydia_Pintscher do you know how to best proceed from here?

Meh, you're right, I didn't think about this. It should be possible by adding https://www.mediawiki.org/wiki/Snippets/Open_specific_external_links_in_new_window to https://www.wikidata.org/wiki/MediaWiki:Common.js.

@abian could we force the link to open in a new tab? Because on Wikipedia it currently open in the same one. That I would find very intrusive because in that instance we'd be forcing the editor to change the wiki which can be disorienting and disruptive to their workflow.

Hey @abian, you are absolutely right. Thanks for making this ticket!

@Greta_Doci_WMDE does that help you to finish the task?

Thank you for @Volker_E !

since the help icon is not an overall icon but used with every statement etc. it should stay with the other icons. We don't seem to have an overall help icon on the page that is visible at all times. If we need something like that is a different topic.

Hi @Greta_Doci_WMDE, sorry for not replying for so long.

@thiemowmde @WMDE-Fisch can you help here?

I forgot the second issue with the bubble!

Hi @Gopavasanth and @Lea_WMDE

@Gopavasanth I had a look at your proposal and i think that it could cause potential problems if we add the help icon into the bar. we'd have to think of how it should behave when the rev slider is opened since the pin isn't visible when closed. We would be causing a jumping behavior because the icon would slide in between the help and the arrow.

@Volker_E If the help icons are being overhauled then I think we should have the updated version in the rev slider as well. A patch would be much appreciated.

Can I ask you what concern you have with displaying the year at all times? If it interferes with an existing workflow or we have not thought of an edge case where it would cause problems, I'd love to hear about it!

In T136104#4674256, @IKhitron wrote:

No, I can't, because of mobiles. But I can say: everyone sees the tool for the first time only once in their life. In all the rest uses they already know how does it work.

That's a good question. I think it helps give perspective in all cases, not only when the page has been around for several years and even then there's an argument to be made for having the year everywhere.

I've updated the mocks to better show how i imagine the time stamps:

Hi @wassan.anmol117 i'm really sorry for the late reply. I have this on my schedule for next week and will post the mocks here when I have them. Thank you for your work so far!

Hi @wassan.anmol117 I do not have my own testing environment so I can only test things that have been deployed to the test wiki.

Hi @wassan.anmol117 please let me know when it has been merged so I can have a look on beta.

Are both the same size already? When you get the svg it has a "default" size with a frame. My question is, does one of them have a wider frame than the other or does the pin have a bigger height?

Hi @wassan.anmol117 , I'm not sure how you imagine a permanent tooltip to look like. Could you elaborate or provide a quick sketch?

would adding a "prefer recent" option solve the issue?

@Lea_WMDE this ticket should be closed because of T202370, right?

What does the "may add" mean? Under which criteria will there be an edit made and under whose name? I think this is smth that should be made transparent since that could influence the editing behavior i assume.

looks fine to me. I don't think the white space is a problem, but rather frames the area quite nicely.

oh awesome! I think it got fixed along with the issue with highlighting the first result!

I was checking the OOUI widgets and some general UI patterns out there to see if there's a way to display this already.

yo @Tim_WMDE , thank you for your input.

Hello @Tim_WMDE @kai.nissen ! Just looked at https://spenden.wikimedia.de/contact/get-in-touch and it looks very nice.

the colors are of the Wikimedia color palette, so the green is okay IMO

I think the difficulty with "preview" is that this label is already used for a specific functionality on wikis and here it would be slightly different. Additionally it would make sense to keep the labeling of buttons consistent so if we go with "change title" (which I agree is the better option) then we should also go with "change file info".

Hey @thiemowmde and @Lea_WMDE

done. ping @gabriel-wmde is this still in scope and are there any questions/remarks from your side?

If that would work for you, then I'd change the mock and ticket accordingly and we'd have one field for both? @tmletzko

@Tonina_Zhelyazkova_WMDE you're right. The x looks really out of place for me though. Is that the standard monobook X or are we adding some OOUI X there?

@tmletzko Is the SpendenID helpful in identifying the person contacting you? If so, I would definitely recommend adding it to the form. If I have such an ID i'd expect to be able to input it somewhere, similarly to a customer ID in an online shop for example or an order number. I would have a field called Spenden-Id (falls vorhanden) for example.

If we drop below the screensize where the 3 column view works we switch to 2 columns, kind of like so:

I agree, but I also think that "not saved" is more clear. "your version..." does not convey that the other version is saved, and yours isn't unless you compare the time which is not written in a way that makes it super easy to do. So it's important to convey that if you cancel everything now, your edits will be lost, because they're not saved anywhere.

I think I'd put it next to Your version instead, I feel like that makes a bit more sense then the date and time.

Can you tell me in how far the topic is used to identify the messages? My assumption would be that the subject lines are often quite vague like "Question" for example and that the names are rather used to find a certain question.

About what should be visible when using backspace and the pill becomes editable: that should without question be the string and not the namespace ID.

I actually want to suggest that we rethink whether "betreff" should be there at all.

Hi @Mooeypoo and @Volker_E ,

@Tonina_Zhelyazkova_WMDE I just realised, I can't really test that because advanced search is a beta feature that only logged in users can use.

Hello @Volker_E and @Mooeypoo

@Pols12 thank you for your feedback. I think you are right about the colon. I removed it from my mocks except for the second one where i feel it's necessary. The indicator is in the standard position for OOUI elements. It would create an inconsistent interface if we were to move it to a different location. I hope the addition of verbs, as you suggested, will make it seem more actionable.

@Lea_WMDE I've looked through the big wikis and picked the namespaces that have occurences in multiple wikis. The rest of the namespaces get a fallback icon .

@MichaelSchoenitzer_WMDE you're absolutely right.

That's what I got from Lea and that's what Stas will update if I understood correctly.

Looks good. Thank you!

@gabriel-wmde I've updated the mock. Can you let me know if it works this time?