User Details
- User Since
- Feb 9 2021, 9:09 PM (138 w, 4 h)
- Availability
- Available
- LDAP User
- Unknown
- MediaWiki User
- NAyoub (WMF) [ Global Accounts ]
Thu, Sep 28
Could we re-use the existing messaging from desktop on mobile?
Wed, Sep 27
hi @kostajh & @aishwaryavardhana, apologies for missing your comments.
Tue, Sep 26
Wed, Sep 20
After discussion on Slack and with @ppelberg, we've decided to move forward with the following option including a neutral-progressive button:
Tue, Sep 19
Here's the updated, latest version of the mock-up design for the Reporting page. [1]
Mon, Sep 11
Thu, Sep 7
Wed, Sep 6
Tue, Sep 5
Aug 24 2023
Great point, thank you @Esanders – I agree with the new alignment you're proposing.
Aug 10 2023
@ppelberg the above responses look great to me with the single caveat that "common knowledge" might be a) paradoxically not universal and b) hard to translate into other languages (it would be slightly wordy in French for instance: "de notoriété publique"). In light of that, what do you think of changing that to "widely known" / "commonly accepted" or something else along those lines?
Thanks for your feedback and flagging those @ppelberg.
Jul 20 2023
Jul 14 2023
Jul 12 2023
Jul 10 2023
Jul 8 2023
@Esanders At the moment let's only apply the debounce time for desktop.
Jul 1 2023
Jun 29 2023
Following an offline conversation with @ppelberg, we decided to use the message shared above by @RHo[1] with a small change in the second sentence to emphasize the notification aspect of future edits instead of credit:
You are not logged in. Once you make an edit, a temporary account will be created for you. Learn more.
Log in or Create an account to get notified about your edits and to access other features.
What about this option?
Thanks a lot for your feedback, @kostajh!
Here are a few options for different UX copies that are being explored – what do you all think?
Current | Option 1 | Option 2 | Option 3 | Option 4 |
---|---|---|---|---|
Warning: You are not logged in. Your edit will be attributed to an auto-generated name by adding a cookie to your browser. Your IP address will be visible to trusted users. If you log in or create an account, your edits will be attributed to a name you choose, along with other benefits. | You are not logged in. Your edits will be linked to a temporary auto-generated account while your IP address will be visible to trusted users. For a personalized experience and additional benefits, log in or create an account. | You are not logged in. Your edits will be linked to an unregistered temporary account while your IP address will be visible to trusted users. For a personalized experience and additional benefits, log in or create an account. | You are not logged in. Your edits will be linked to an unregistered temporary account while your IP address will be visible to trusted users. For a personalized experience, attribution of your edits and other benefits, log in or create an account. | You are not logged in. Your edits will be linked to an unregistered temporary account while your IP address will be visible to trusted users. For a personalized and enhanced experience, log in or create an account. |
Jun 15 2023
@MNeisler I just added the new UX desktop flow to the Miro board for Edit Check Measurement
Jun 12 2023
Jun 8 2023
Jun 7 2023
Mar 15 2023
Feb 25 2023
Agreed, the demo looks really nice! Regarding the background color, I believe we should be using #eaf3ff to comply with the design system color tokens – which might already be the case in the patch, the blue looks very similar.
More information can be found in the design system documentation here or below :)
Feb 14 2023
[new exploration] more conversation-like:
Jan 31 2023
Jan 23 2023
Jan 19 2023
Jan 12 2023
The revised scope looks great – I don't imagine the absence of T267444 having an impact on this initial deployment of Page Frame.
Nov 10 2022
Same bug as T320820?
Yes exactly
This looks amazing! 👏
Oct 24 2022
Oct 21 2022
Oct 20 2022
Oct 13 2022
Oct 12 2022
Thanks for the ping @ppelberg and for spotting this @alexhollender_WMF!
I agree with @Esanders: although styled as links, these are buttons so :visited colour doesn't make sense here.
Design QA
Looks great! Two observations:
- The "i" icon looks slightly different than the one on the mock but it's normal – the OOUI icon has been updated since then and the patch demo has the latest one.
- Not directly related to this task but the "add topic" button is missing the talk icon on this patch demo – is it normal since it's Patch Demo or a bug? @Esanders
Sep 13 2022
Great spot @Tacsipacsi thank you for sharing! We won't be working on this right now but it's great to know for the future.
Thanks a lot @bmartinezcalvo for all the context!
Sep 10 2022
Thanks @Esanders Looks great!
Sep 9 2022
Sep 8 2022
The "current spacing" in the original task looks wrong to me: The spacing between the last comment and the next heading is much bigger that it actually is, and as a result your proposed spacing is a large change. I'm not sure we want to make it that large.
Yes exactly that's the discrepancy between Figma and production I was mentioning. I think it'd still be good to have more spacing between the last comment and next heading compared the last patch demo (screenshot below):
@Esanders thanks for the patch demo! I noticed some discrepancies between the original Figma and the patch demo so I adjusted directly on the demo:
Sep 2 2022
Just added the mocks and reviewed the reqs – looks all good. Moving this back to you @ppelberg :)
Aug 29 2022
Aug 27 2022
@Tacsipacsi Yes that's exactly what converged on :)
Aug 26 2022
Looks perfect @ppelberg thanks for the updates!
Hi @Esanders, here are the relative measures for the spacings – hopefully the original Figma file is well coordinated with what's in production, otherwise will refine :)
Yes, that's a good point @Tacsipacsi. The objective is not to flood users with notifications, simply to remind them that they can adjust their notifications settings if they want to – especially for less advanced users who might have not explored their preferences. This meta-notification wouldn't be displayed often, only if you receive a significant amount of notifications in a short time or if you have a lot of unread ones.
To be consistent with the visual design of Talk pages on the apps, it's best to go with bold text for the headers on mobile.
Aug 25 2022
@Samwilson
For the circular progress indicator (which I imagine will have an indeterminate load), I based the design on Google's Material UI component with Accent50 (#3366CC) color token from our design system.
Attaching the SVG and specs below:
SVG | Circular line (2px line width) | Loading component bounding box (16px) |
Aug 24 2022
My gut is telling me to provide a well padded icon and go with oo-ui, plus it helps us standardize elements/design system. Can we add that one line change in? CCing @nayoub for visibility
I think this is intentional, with the idea being that this is an advanced feature and we don't want to distract from other more important links. Other sites use similarly muted styling (Twitter, Phabricator etc).
Great point @Esanders! I agree that adding another verb could cause some confusion and +1 on the translation community finding the appropriate copy.
are there any adjustments you'd like to see made to the naming of the browser tab prefixes before we move forward with implementing this?