Hey @Ramsey-WMF, I have some questions about this one based on comments in the parent task:
Wed, Jun 3
Tue, Jun 2
Fri, May 29
Great, I'll make those updates! We can screenshare early next week to get this one wrapped up.
Thanks @Niedzielski, this is super helpful!
Thanks for the feedback!
Thu, May 28
Hey @egardner, thanks for the thorough explanation. I think the main issue with fading the border out after x seconds is that we don't know how long it'll take for the panel to load for a given user. On my (slow) local site, the border fades well before the statement panel has fully loaded. We could bump up the time to something like 10 seconds, but that still might not cover all users. I'd recommend we either do that and assume it'll cover most users, or go for a JS solution to mimic github's UX.
Wed, May 27
Mon, May 11
This has been covered in the Vue version of the UI, so it can't be QA'd until that's launched.
Fri, May 8
May 6 2020
Deployment plan (flexible; please let me know if you have feedback):
@mwilliams What do you think about moving the message below the main paragraph of text, above the "images for review" heading? If we put it at the top, when it's dismissed, it'll seem like the entire page moves up (we can make this a smooth transition in Vue pretty easily, not so much in the current version). If we move it to below the main paragraph, that paragraph will remain fixed when the notification is dismissed, and only the content below it will move up. Also, for a first-time visitor to the page, I think reading the main paragraph then reading the notification will make more sense than reading the notification then the main text.
May 5 2020
May 1 2020
Apr 29 2020
Hey @mwilliams, do you think the border around the linked-to statement panel should persist the entire time the user is on the page, or disappear after a certain time or event? I'm thinking of a couple of scenarios:
Apr 28 2020
Apr 27 2020
@Ramsey-WMF on it, sorry for the delay!
Hey @Etonkovidova – the use case for somevalue that we're supporting on Commons is a bit different than on Wikidata. After discussing with Multichill, we decided to support the use of somevalue to represent a missing Wikidata item rather than the broader Wikidata definition (i.e. some value exists for this property, but we aren't saying anything about that value). For this reason, we're only supporting somevalue/novalue snaks for the Wikidata item property type and have used different language for somevalue in the UI.
Apr 21 2020
Apr 20 2020
Apr 16 2020
There are 2 ways we can add license metadata:
Apr 15 2020
Hey @Raymond, thanks for raising this. As of today, hidden categories should no longer be showing up. Can you please confirm if you're seeing that now?
FYI @CBogen I found a relatively painless way to accomplish this so I went ahead and opened a patch so we can get this on prod sooner. We'll handle it in the Vue port as well.
Apr 13 2020
Apr 10 2020
Apr 8 2020
I recently refactored the suggestion component in Machine Vision to use CheckboxMultiselectWidget, in case that's helpful. See SuggestionsWidget in this patch, or check out the current code (JS | LESS) in which we've fixed the checkbox animation issue by using transition instead of animation (thanks @Catrope).
Apr 6 2020
Based on Timo's comment above, we're going to use the natural language fallback chain rather than the Babel chain for labels. We're already removing suggestions whose labels don't have a value in the user's language(s), and the "add custom tag" tool gives users an action when few or no suggestions are presented.
Apr 2 2020
Apr 1 2020
Yeah, uploads are assigned to users when suggestions are fetched from the provider, so existing uploads assigned to you will remain but new ones that you revert shouldn't be added to your stack.
Mar 31 2020
Mar 25 2020
Mar 23 2020
Mar 20 2020
Mar 19 2020
Mar 18 2020
Mar 17 2020
Mar 16 2020
Mar 12 2020
Mar 11 2020
Update: we've opted to add somevalue/novalue items as soon as they're selected from the dropdown to mimic the behavior of entities selected from the autocomplete widget, gif below:
@Ramsey-WMF To answer your first question, I wasn't able to display the error message directly above the qualifier because the error response we get back: