Page MenuHomePhabricator

If blocked, MobileFrontend does not block you from adding a new section on talk pages (but then MW stops you if you're not allowed)
Closed, ResolvedPublic

Description

This is unlike page editing, which is inconsistent and a poor user experience.

Event Timeline

Jdforrester-WMF raised the priority of this task from to Medium.
Jdforrester-WMF updated the task description. (Show Details)
Jdforrester-WMF moved this task to Backlog on the MobileFrontend board.
Jdforrester-WMF subscribed.
Nirmos renamed this task from If blocked, MobileFrontend does not blocks you from adding a new section on talk pages (but then MW stops you if you're not allowed) to If blocked, MobileFrontend does not block you from adding a new section on talk pages (but then MW stops you if you're not allowed).Feb 18 2019, 3:27 PM
Jdlrobson changed the task status from Open to Stalled.Mar 26 2021, 10:19 PM
Jdlrobson subscribed.

Stalled per T278590

ppelberg added subscribers: Ryasmeen, ppelberg.

@Ryasmeen moving this over to #EditingQA to verify the issue this ticket is reporting is NOT present within the mobile Reply and New Discussion Tool.

ppelberg claimed this task.

@Ryasmeen this ticket appears to be similar to T248024 [i] in so far as it too seems to be resolved considering it's been tagged with Verified [ii] and not moved to Ready for sign off.

If the above is not the case, please re-open this task and comment as much.


i. T248024#7813054
ii. T111741#7721194

I don't recall exactly what the experience was before now, but I just did a quick test of the current functionality. When I try to add a new section from a blocked account, I can click Add Topic and write my text, and then trying to save the edit displays:

image.png (111×329 px, 4 KB)

(I'm not sure what the little red bell icon is for)

On desktop, clicking 'New section' prevents you from writing anything and gives you a more direct message informing you that your account is blocked and guidance on how to understand/appeal this.

Ideally I'd think that users should be given a similar message on mobile, rather than a generic 'you don't have permission' message, but I'm not sure if that's what this task was getting at originally, or if that's another issue.