Page MenuHomePhabricator

Lack of next steps for new users on mobile devices when attempting to edit a protected page
Open, NormalPublic

Description

Specific requirements:

Use Safari browser to edit frequently vandalized English Wikipedia page on iOS device

As a new user not logged in attempted to edit a page, a notification popped up with the notification "This page is protected to prevent vandalism". It also displays a locked pencil. However, it does not provide advise as to why it is locked or what to do next. This discouraged a new user that did not know they needed to create an account or attempt a page that is not as likely to be protected.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 12 2018, 1:13 AM

At least (on English Wikipedia) you have that when you clock on "view source":


(Image is from @kostajh)

Esanders added a subscriber: Esanders.EditedOct 12 2018, 4:13 PM

In general we don't show any edit notices[1] in either of the mobile editors.

  1. https://en.wikipedia.org/wiki/Wikipedia:Editnotice
ovasileva triaged this task as Normal priority.Oct 16 2018, 9:07 PM
ovasileva moved this task from Needs triage to Triaged on the Mobile board.
matmarex moved this task from Research to Q4 on the VisualEditor board.Oct 31 2018, 4:40 PM
matmarex moved this task from Q4 to Research on the VisualEditor board.
matmarex added a subscriber: matmarex.

(That was a miss-click. I hate workboards.)

matmarex removed a subscriber: matmarex.Oct 31 2018, 4:41 PM
JTannerWMF moved this task from Research to Q4 on the VisualEditor board.Dec 12 2018, 2:49 PM

@JTannerWMF @marcella can you verify if this describes the same issue as T208827?

@JTannerWMF @marcella can you verify if this describes the same issue as T208827?

This is not quite the same, though they are certainly related. This task is specifically about guiding the user towards next steps, "to create an account or attempt a page that is not as likely to be protected." It is not about improving access to source/wikitext. Does that help @alexhollender?

@marcella yes thank you for clarifying. It seems like we should possibly think about the following cases:

protected for all users (except admins)protected for logged-out users
logged outrecommending logging in might not make sense here, instead maybe just offering "View source"?encouraging creating an account or logging-in makes sense
logged inoffering "View source"N/A

It does seem like it might make sense to combine this task with T208827 and make it broadly about improving UX for trying to edit/view source protected pages for both logged-in and logged-out users, since it seems like any solution here should be considerate of the solution in T208827 and vice-versa. Thoughts?