I just want to stand on land.
- User Since
- Oct 9 2014, 1:53 AM (223 w, 1 d)
- IRC Nick
- LDAP User
- MediaWiki User
Fri, Jan 11
That work is now being tracked under JSDoc WMF theme.
Thu, Jan 10
Wed, Jan 9
@Tchanders from your previous comment I understand that its going to be tricky to add help text (tooltip, or inline) on the radio options. I wanted to ask if its going to be possible at all, or should we be thinking of other solutions?
Mon, Jan 7
Sun, Jan 6
Fri, Jan 4
Thu, Jan 3
I think we can have the same design with different wordings. The user might get a bit confused by seeing an empty translation interface.
That makes sense @Niharika. I think that we should revise the text and sub-text though, maybe remove the links from there at least?
Wed, Jan 2
Are we able to tell the difference between images that have text that cannot be translated and images that just don't have text? Is this a special case of T210218: Show message when loading an SVG with no translations, or something completely different?
Thu, Dec 20
That looks about right. I think the only difference left is to reduce the vertical margin of the loading indicator. On the prototype you can see the modal by going to the → → Wikidata Contributions. I think our markup is the same.
After discussing this with @jmatazzoni, here is an option that keeps the saves what we can immediately, and keeps the unsaved changes in the textarea and shows the error indicator there.
|Initial||Adding new items||After hitting save|
Wed, Dec 19
- Our understanding is that hide/show is not part of the supported style guide, and that active/inactive is the preferred treatment. Is this not the case?
Yep, we don't use that pattern anywhere else, was just wondering if we considered it for this. Happy to go ahead the way it is 🙂
@Samwilson, you had mentioned that we'd be able to do something like Leaflet? It'd be cool if that is possible 🙂If not we could use the ButtonGroupWidget with the + and - icons being overlaid on the image. We would also want to show the ✋mouse cursor on hover to let the user pan around.
A quick question about your comment on our doc — we'll need the upload progress state to completely block all other interactions, right?
I think we can make the text #000 here. What do yo think about the subtext, @Niharika?
Can we make a minor change in the design? Prefixing Untranslated before every label might be cumbersome for the user to read through every time. Can we move it to the bottom and make it smaller?
Yep @Samwilson's idea makes sense, let's go with that.
Will we be able to reliably do this for different sizes of images?
Dec 19 2018
Dec 18 2018
Dec 9 2018
Thanks for your work on this, @Stibba
Dec 5 2018
Hey @Sochin67, thanks for raising the ticket. Unfortunately, I am not working on this anymore, so I've added some people who might be able to help.
Dec 4 2018
I don't think we should repeat the word "pages" or "pgs.", it gets redundant. How about we only add the "pages" label to the first option?
Dec 3 2018
@MusikAnimal, is it possible to have the dropdown be wider than the input field?
Nov 29 2018
Nov 27 2018
Nov 26 2018
Possibly happening because the fonts have been defined as HelveticaNeue-Bold, Helvetica Neue which are pre-installed on MacOS. It shows up in the default font on other OS's. Should add sans-serif here.
Nov 25 2018
Nov 22 2018
Thank you for working on this @Arcayn
I guess 2000 should be fine, we can ask @Mooeypoo to test once this is done and adjust later if we feel the need 💻
I just remembered that @Mooeypoo had shared that the tool becomes useless on large screens. I think we should limit the interface width to 1400px (CSS, not device pixels… retina 👀).
I don't think this means that we need to show two languages as the source language, they can still be shown as separate. If you select Chinese you get all Chinese translations, including the ones that are shared by Japanese (and the same goes if you select Japanese). And while saving if the value doesn't change we can let it be the way it is, and if it does we can split up the <text>:
Will some of these problems go away now that we are planning to T209900: Switch to using ULS as a backend for languages instead of using the ULS dialog?
I am guessing that we'd need to display, and allow to search using the following:
- Language name in the UI language - अंग्रेज़ी (English, in Hindi, and written in Devanagari)
- Language name in the language itself - English
- Language code in latin - en
Nov 20 2018
Does the user need to be taken to a special page to download the report? Do we know the design requirements for the Special page as well? Would it be ok to trigger the download directly from the "User profile" tab?
Thanks for your patches @Platonides :)
Nov 19 2018
Nov 16 2018
@Platonides, since we won't be making the rest of the changes, would it be ok to close this task now?
@Volker_E Do you mind if I put this task up for GCI?
Thanks for the screenshots! The Gitlab font choice looks good. @Volker_E, is it ok if I put this task up for GCI?
Thanks for the patch @Arcayn. Looks good.
Thanks for the patch Mogmog123. Looks good.
Added a proposed design, looking for feedback 👨🏽💻