I just want to stand on land.
- User Since
- Oct 9 2014, 1:53 AM (258 w, 5 d)
- IRC Nick
- LDAP User
- MediaWiki User
Thanks for all the clarifications, @MusikAnimal!
I am thinking we should clearly mark the parts of the page on which WhoWroteThat won't work (Templates, Images, Tables?). A way to do that would be to reduce their opacity which would make them look disabled. We can choose to have no mouse events on them so that people don't accidentally click on them and navigate away when they actually expected to see the popup.
Tue, Sep 17
So if I understand correctly, the users who haven't confirmed their email addresses see the following message (as does everyone else):
Mon, Sep 16
I am not familiar with some of the standards around the current NPP design, so, I had two queries:
- What is the difference between the red text that shows up after the title like "No Citations", "Orphan" etc. and Potential issues like 'Copyvio'? I don't understand the conceptual difference between the two.
- I see a few different icons before the title: , , . Should this change if the username is in the article?
Ah, that makes sense. I think lets keep it as is for now and figure out what needs to be done once we have results back from the usability tests.
The text wrapping looks good, I think we can go ahead with it. Thanks for posting the screenshot 👍🏽
Wed, Sep 11
Tue, Sep 10
Mon, Sep 9
@cscott would you be able cut a new release? Happy to do it myself if you can add me on NPM.
- Form states
The way to enable/disable this preference would be a checkbox in Special:Preferences. It'll only show up if the user has confirmed their email. I can think of two places where this setting could be:
Given that the edit summary could in some cases could load very fast (less than 100ms) we don't want a case where we flash the animation for a very small amount of time. I am taking some inspiration from the font-display browser behavior here.
@Samwilson, I think it would also be alright to increase the width of the pop-up enough to fit IPv6 addresses. There are currently two popups sizes in the Zeplin—250px and 320px. Which one is being used screenshot above?
The WhoColor tool currently uses the tabs on top-right, and is represented as a text item (in the same hierarchy as Read and Edit). As you mentioned, we have a few options on where to put this tool:
- Top-left tabs (Article | Talk | Who Wrote That)
- Top-right text tabs (Read | Edit | View History | Who Wrote That)
- Top-right icon tabs (Star icon | WWT icon)
- Tools sidebar
- User menu on the top right (I don't really think this is an option, but still noting it here)
Here is the example I had in mind — https://en.wikipedia.org/wiki/User:Prtksxna/citation-test.:
Thu, Sep 5
Should we regenerate the OOjs documentation to test before closing this task?
@ifried, I agree. Always having a full stop . would also be better when there is no edit summary to show.
Wed, Sep 4
Thu, Aug 29
Tue, Aug 27
If the edit summary is the only thing that we'll be waiting to load we could use a content placeholder with an animation, and then switch it out with the summary once we have it - https://codepen.io/prtksxna/pen/OJLmVXZ (data will load after 3 seconds)
Mon, Aug 26
Yeah, so the current loading state doesn't have the close icon. If we suspect that the tool can be in this mode longer than a few seconds we should definitely add a close button here as well.
So, will we need both partial and full loading states? What all would have already loaded in the partial state?
Ooh, thanks for this @MaxSem 🤩So the proportion of no(~¼), unconfirmed(~½), and confirmed(~¼) emails looks something like this:
Will the average (or median) be calculated since the page was created? Or will it be the average of that week or something?
Aug 21 2019
Aug 20 2019
Aug 19 2019
I can see how in its current form the target can be confusing. I see two main reasons for this:
- The hover state only changes the background color and the change isn't drastic so is easily missable.
- Since the button for the diff (the area we clicked to open the diff) and the revision target are touching each other its not clear if they're connected or separated. I clicked on it a bunch of times accidentally thinking that it'd close the diff.
Aug 16 2019
@ifried, does this still need any design work?
Aug 14 2019
@MusikAnimal, I didn't know about preload parameters, yeah that is exactly the kind of thing I was hoping for.
Aug 13 2019
|Issue||Time it'll take to resolve||Message|
|Page is too long, time out||Seconds||Something went wrong, Try refreshing the page|
|Page not yet in WikiWho database||Hours||We are gathering the data for this page now. Check back in a few hours.|
|Too many requests||Minutes||We weren't able to make this request. Try again in a few minutes|
Aug 12 2019
Thanks for all this information, @MusikAnimal 🤩
Aug 8 2019
Aug 2 2019
I don't really need this any more, so no need to help me debug 😊
Happy to provide more info if you'd like though.
Yup, the .env file is correct, and I am not trying to log in. When I try to navigate to - http://localhost:8042/File:Speech_bubbles.svg I get an error. Here is the stack trace:
Jul 27 2019
This should get deployed automatically in a while. Thanks for spotting and closing the issue, @Ammarpad 😊
Jul 24 2019
Disable clicking anywhere on the page while content loads from the WhoColor API
Jul 23 2019
Jul 22 2019
I agree the link icon would be misleading, and so would linkExternal. @Esanders, is it going to link to the template’s documentation? If so, then yeah, the helpNotice makes sense here.
Good idea @Mooeypoo! I've updated the screenshots above.
Thanks @Samwilson, that worked. Also, is there a workaround for the WIKI_URL if I don't have a local wiki?
This seems almost fixed now. The starting of the leaflet box and the input are off just by a pixel.
I see now, thanks @TheDJ! The ratio of the screenshot threw me off and I assumed it was a mobile.
Jul 18 2019
I took @Samwilson's help to understand this navigation a bit better. I now understand that the icon currently represents two states:
Blue bar to show up under the top tabs and should be sticky.
The maximum character limit for edit summaries is 500 characters, I think we'd be able to fit that. I am also considering making the popup wider if we do that.
We can choose whether or not to show the extra user information. With the visual representation of highlighting everything that the user has written I don't think its necessary.
Jul 16 2019
Jul 9 2019
Something like this?
Jul 8 2019
Jul 4 2019
Jul 3 2019
I am hoping that we can use the same blue bar to show different states of the tool. Ottawahitech had suggested that we don't cover the View History and Edit tabs, and I think that makes sense. We should however make it sticky so that its visible even when the user has scrolled down.
Thanks @Mooeypoo! Quick question, is it possible to have markup inside OOUI popups like headings and stuff, as is the case with GuidedTours?
@Mooeypoo I wanted to confirm that this wont be the actual GuidedTour since the code is outside of MediaWiki. Will we be able to style it however we like?
Jul 1 2019
No, it is resolved now. Sorry, I forgot to close it.
Jun 27 2019
Jun 19 2019
May 31 2019
@Niharika Do we want to support mobile screen sizes for the translation page too?
Lets add a label on top of the dropdowns ( "from:" and "to:")
How about we scroll the page down (enough to hide the header) as soon as an input gets focus?
May 30 2019
Could we please get tracking snippet that we can include in the page, thanks!