oh i didn't know that one existed @Lucas_Werkmeister_WMDE. Should i delete this one?

Hello @ArthurTaylor, let's just reproduce exactly the error text from Wikibase production everywhere consistently with the design provided.

Hi @ArthurTaylor, on the native select that this dropdown calls the values would be complete/not truncated! is this possible?

Hi @ArthurTaylor, this is totally my bad as i failed to describe it in the ticket. But my idea was to always truncate the dropdown content with ellipsis - 10 characters tops. Here the example o coordinates:

Hi @Arian_Bozorg & @Lucas_Werkmeister_WMDE, i think it is a good improvement!

Uh i am going to assign this to me and have a look! totally forgot this was a thing

Hi @Lucas_Werkmeister_WMDE , this is such an edge case that honestly i am fine with the solution! When there is an error being clicked, it is more important that people read the error... and this happens. Thank you for figuring it out

@Sarai-WMF Thank you very much for your quick and thorough reply and next time i will ask the steering committee. Have a great day!

@Sarai-WMF Hi Sarai! i got your name (but not your contact) contact from the UX team :)

Hi @AudreyPenven_WMDE , sorry i didnt see these comments before! The current adjustment looks fine to me :)

when i designed this error it was under the assumption that it would be fairly easy to put the grey box inside the error message... if this is not the case, we could have a meeting, discuss possibilities and come up with a different design option!

Hello @ArthurTaylor and @Lucas_Werkmeister_WMDE and thank you so much for this! could we possibly have a meeting in the new year to talk about this - i am not sure i understand it fully, and need to flow these learnings into the design of https://phabricator.wikimedia.org/T409454 and https://phabricator.wikimedia.org/T409453!

Hello @AudreyPenven_WMDE, answering to your question : "if the starting value should be also having a gradient fade like the end"

Hi @ArthurTaylor, it is not a mistake, and i explain why this is so in the original ticket https://phabricator.wikimedia.org/T400676:

Hi!

• “The publishing button becomes blue (default)” – while still being covered? - those 2 things are independent from each other. Valid output = button is blue, even if covered.
• “When the user decides to publish, we save and publish whatever was showing at the date rendering display in the moment of clicking.” - good point, it only becomes blue when the output is valid, as is on desktop. I forgot to cover that case of invalid input and will do so now.

Hi @mahmoud.abdelsattar.wmde, on the other lookups you have the option to type in the form as well. This is one of the few lookups where you mandatory need to pick an item that fits your description, and whatever you write is not "publishable". Hope this helps

@Lucas_Werkmeister_WMDE but good inclusive point, i hadn't considered it!

@Lucas_Werkmeister_WMDE there is no version of this image where the left hand holds the phone, but i wouldn't think there is a problem, since there is nothing indicating direction in writing on the image itself, and we all hold our phones with any hand available at a given time. @mahmoud.abdelsattar.wmde would you confirm?

hello @Lucas_Werkmeister_WMDE. You are right but, error messages always only happen in the edit modal anyway - when there is a publish error the user simply stays where he was, doesn't go back to the main page and cannot click the edit button again. Therefore it shouldn't matter if the code would cancel the error message, because this case never happens anyway. I think?

yup.ts done