Page MenuHomePhabricator

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

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
Jdlrobson added a subscriber: Jdlrobson.

There's not much help on desktop either. :(

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 Medium priority.Oct 16 2018, 9:07 PM
ovasileva moved this task from Needs triage to Triaged on the Mobile board.
Jdlrobson moved this task from Backlog to Tracking on the MobileFrontend board.Oct 18 2018, 6:57 PM
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?

alexhollender added a comment.EditedMay 22 2019, 12:07 AM

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

protected (for all users except admins)semi-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?

JTannerWMF added subscribers: matmarex, ppelberg.

@matmarex proposed a solution in T221328 of:

Problem: When a page is protected, new users get a message like "This page is protected to prevent vandalism". It does not provide advice as to why it is locked or what to do next.
Solution: Guide the user to create an account or attempt editing pages that are not protected.

It looks like there is an open question to @marcella on this. How can we unblock this to start building?

Esanders renamed this task from Lack of next steps for new users on mobile devices when attempting to edit a protected page to Lack of next steps for new users on mobile devices when attempting to edit a semi-protected page.Jul 3 2019, 2:27 PM

Looks like the original report is talking about "semi-protected" pages which are only uneditable by logged out users, so I've updated the title.

Looks like the original report is talking about "semi-protected" pages which are only uneditable by logged out users, so I've updated the title.

I wonder if it makes sense to consider both cases (protected & semi-protected) here? See T206829#5202751 in case you didn't already.

Looks like the original report is talking about "semi-protected" pages which are only uneditable by logged out users, so I've updated the title.

I wonder if it makes sense to consider both cases (protected & semi-protected) here? See T206829#5202751 in case you didn't already.

I did, but I think in the full-protected case we can't make the experience much better for the user, so we may want to give that a lower priority.

I think we should use the same messages that are shown on desktop. The English Wikipedia message looks actually quite helpful:

The most important reason to do so is that there are more protection levels than semi and full, and they are different on each wiki, depending on the local policies/configuration. For example, English Wikipedia has extended confirmed and template protection as well; Polish Wikipedia has medium protection.

There is already a system in place to define messages for each of these and display them in the appropriate case, and I think it would be impractical for us to maintain new messages, and inconsiderate to task the communities with maintaining an additional set of new messages instead.

The tricky part is figuring out how to adapt the styling of existing messages to the mobile interface.

The tricky part is figuring out how to adapt the styling of existing messages to the mobile interface.

Assuming that is an appropriate amount of text and detail to show on a mobile device.