Page MenuHomePhabricator

[minor] Non-structured task articles - post-edit dialog "You've published an edit! " message requires scrolling up
Closed, ResolvedPublicBUG REPORT

Assigned To
Authored By
Etonkovidova
Sep 14 2022, 9:52 PM
Referenced Files
Restricted File
Feb 28 2023, 8:06 PM
F35521178: image.png
Sep 15 2022, 10:14 AM
F35521176: image.png
Sep 15 2022, 10:14 AM
F35520663: scroll_up_post_edit.gif
Sep 14 2022, 9:52 PM
F35520679: scroll_up_post_edit2.gif
Sep 14 2022, 9:52 PM
Tokens
"Like" token, awarded by kostajh.

Description

Steps to replicate the issue (include links if applicable):

  • On Special:Homepage on testwiki wmf.1 go to any of non-structured tasks
  • Go toward the end of the article - find an article with a reasonable length, not a short one.
  • Make some edits and publish.

What happens?:

  • The post-edit dialog appears, but the upper part - the green message box won't be visible. To see it, a user needs to scroll up.

In the gif below - the scrolling up is done manually.

scroll_up_post_edit2.gif (690×1 px, 2 MB)

What should have happened instead?:

  • The post-edit dialog for non-structured tasks should behave in the same way as it behaves for structured tasks:
    • add a suggested link that is placed close to the end of the article and publish
    • the article will scroll up and both parts of the post-edit dialog will be displayed.
    • put the success message just above drawer, like we do on mobile

image.png (896×1 px, 591 KB)

image.png (1×1 px, 119 KB)

Software version (skip for WMF-hosted wikis like Wikipedia):

Other information (browser name/version, screenshots, etc.):

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
kostajh added a subscriber: KStoller-WMF.

@KStoller-WMF perhaps we should put the success message just above drawer, like we do on mobile?

image.png (896×1 px, 591 KB)

image.png (1×1 px, 119 KB)

Otherwise, we could use position: fixed on desktop to pin the toast message towards the top of the viewport.

As a side note, do you all remember if there is supposed to be a "Close and edit again" prompt in this dialog?

As a side note, do you all remember if there is supposed to be a "Close and edit again" prompt in this dialog?

It was removed in favor of a collapse icon in T301603: Newcomer tasks: increased flexibility at post-edit dialog.

Aklapper renamed this task from [minor] Non-structured task artciles - post-edit dialog "You've published an edit! " message requires scrolling up to [minor] Non-structured task articles - post-edit dialog "You've published an edit! " message requires scrolling up.Sep 15 2022, 1:56 PM

@KStoller-WMF perhaps we should put the success message just above drawer, like we do on mobile?

That makes sense to me. Placing the confirmation message there also helps draw attention to the "Edit another suggestion" call to action, which could funnel more people into trying another suggested edit.

@KieranMcCann Does this approach sound OK to you, or do you have any concerns with this change?

@KStoller-WMF Yes I’m happy with that approach. I think it makes sense for the two messages to be in the same vicinity of each other on the screen.

Change 888763 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] Post edit: show the success toast message tied to the drawer

https://gerrit.wikimedia.org/r/888763

Sgs changed the task status from Open to In Progress.Feb 13 2023, 6:30 PM
Sgs moved this task from In Progress to Code Review on the Growth-Team (Sprint 0 (Growth Team)) board.

FWIW the old behavior was added in T301603: Newcomer tasks: increased flexibility at post-edit dialog, on the basis that it is more engaging/noticeable. I wouldn't mind getting rid of it (IMO it was one of those UX flourishes where the improvement wasn't really proportional with the code complexity it required), but we could probably fix it just by changing the positioning from absolute to fixed.

FWIW the old behavior was added in T301603: Newcomer tasks: increased flexibility at post-edit dialog, on the basis that it is more engaging/noticeable. I wouldn't mind getting rid of it (IMO it was one of those UX flourishes where the improvement wasn't really proportional with the code complexity it required), but we could probably fix it just by changing the positioning from absolute to fixed.

I agree. Tying the apparition of the message to the apparition of the drawer in both positioning and timing seems conceptually incorrect because the message is the feedback from a successful save. If the drawer breaks for any reason we would probably fail to show an edit success message which seems critical for a newcomer. Also if we wanted to stop showing the post edit drawer for any reason we would need to re-think of the placement. I also prefer to fix this issue using fixed positioning rather than undoing the work in T301603: Newcomer tasks: increased flexibility at post-edit dialog and showing it on top of the drawer. Once we resolve T294835: Positive reinforcement: Revise skeleton state and behaviour of the Post-edit dialog, the render of the drawer won't depend on any data request so both message and drawer will appear immediately after save.

What do you think about the fixed positioning @RHo?

FWIW the old behavior was added in T301603: Newcomer tasks: increased flexibility at post-edit dialog, on the basis that it is more engaging/noticeable. I wouldn't mind getting rid of it (IMO it was one of those UX flourishes where the improvement wasn't really proportional with the code complexity it required), but we could probably fix it just by changing the positioning from absolute to fixed.

I agree. Tying the apparition of the message to the apparition of the drawer in both positioning and timing seems conceptually incorrect because the message is the feedback from a successful save. If the drawer breaks for any reason we would probably fail to show an edit success message which seems critical for a newcomer. Also if we wanted to stop showing the post edit drawer for any reason we would need to re-think of the placement. I also prefer to fix this issue using fixed positioning rather than undoing the work in T301603: Newcomer tasks: increased flexibility at post-edit dialog and showing it on top of the drawer. Once we resolve T294835: Positive reinforcement: Revise skeleton state and behaviour of the Post-edit dialog, the render of the drawer won't depend on any data request so both message and drawer will appear immediately after save.

What do you think about the fixed positioning @RHo?

Sounds good, IIRC think we had it at the top on Desktop to match VE save messages only, but I do prefer this behaviour as consistent with the mobile placement and connection to the post-edit dialog drawer. And to confirm, let' use the same distance of 1em between the drawer and the success message. Thanks!

Change 891411 had a related patch set uploaded (by Gergő Tisza; author: Gergő Tisza):

[mediawiki/extensions/GrowthExperiments@master] Post-edit: Use fixed positioning for success notice

https://gerrit.wikimedia.org/r/891411

Change 888763 abandoned by Sergio Gimeno:

[mediawiki/extensions/GrowthExperiments@master] Post edit: show the success toast message tied to the drawer

Reason:

Abandoned in favor of fixed positioning in I2c6f2ce3cc65c77a6147ed4fb1438966d4e5d02c per review comments

https://gerrit.wikimedia.org/r/888763

Change 891411 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] Post-edit: Use fixed positioning for success notice

https://gerrit.wikimedia.org/r/891411

We opted to go for a fixed positioning on desktop; even if that makes the behavior slightly different from mobile not having the success message tied to the drawer in time and positioning gives us flexibility now that other panels are appearing after save. Also tying the toast to the drawer means if the code for showing the drawer breaks we could end up not informing the user about the successfully saved edit. Hope this is good enough for solving the issue.

Sgs changed the task status from In Progress to Open.Feb 23 2023, 7:59 PM
Sgs moved this task from Code Review to QA on the Growth-Team (Sprint 0 (Growth Team)) board.

Checked in enwiki betalabs and testwiki wmf.25 - works as expected.
{F36885025}