Could we re-use the existing messaging from desktop on mobile?

hi @kostajh & @aishwaryavardhana, apologies for missing your comments.

After discussion on Slack and with @ppelberg, we've decided to move forward with the following option including a neutral-progressive button:

Here's the updated, latest version of the mock-up design for the Reporting page. [1]

Looks great, thank you @Esanders & @ppelberg.
Moving to Ready for sign off.

Great point, thank you @Esanders – I agree with the new alignment you're proposing.

@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.

Thanks @Esanders, this looks great for MVP.
@ppelberg I'm assigning to you for next steps.

@Esanders At the moment let's only apply the debounce time for desktop.

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.

Thanks a lot for your feedback @RHo & @ppelberg – these are all great points!

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?

@MNeisler I just added the new UX desktop flow to the Miro board for Edit Check Measurement

Thanks @Esanders & @ppelberg, here are the latest requirements:

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 :)

[new exploration] more conversation-like:

The revised scope looks great – I don't imagine the absence of T267444 having an impact on this initial deployment of Page Frame.

Same bug as T320820?

Yes exactly

This looks amazing! 👏

Thanks, @ppelberg & @Esanders!
Looks great, my only concern is that when the keyboard is opened then I'm not seeing the "Return to reply" button (since the keyboard is on top of it).
I wonder if we should place the button at the top of the screen then?

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:

1. 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.
2. 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

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!

Thanks @Esanders Looks great!

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:

Looks great, thanks @Esanders! Moving to sign off.
cc @ppelberg

Just added the mocks and reviewed the reqs – looks all good. Moving this back to you @ppelberg :)

@Tacsipacsi Yes that's exactly what converged on :)

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.

@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)
circular-loading.svg281 BDownload

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?