[This has been split out of T165535]
When a user is blocked and tries to edit a page, they do not see that they are blocked until the end of the workflow. In web, this is checked before the editor is opened.
When I logged in with my test account and clicked the pencil icon to edit the sandbox, it popped up with an edit window, and I could modify the source:
When I click "Next", it continues to let me save an edit summary.
Only when I click "Publish" after filling in an edit summary does it finally give any indication that the account is blocked.
This block notice is unsatisfactory because it fails to explain or provide a link to a page that explains why the block is there. It also does not name the administrator that placed the block, nor does it list an expiration date, nor does it link to a page with instructions on how to appeal the block.
When an editor is blocked from editing and they try to edit they will have a block message modal show up right after they tap on the editing pencil icon in article view. This stops the editor from making any new edits.
- Modal has 'exclamationmark.octagon.fill' icon
- Block message modal displays full content of the block.
- Modal can be dismissed by tapping 'Ok'
- Editor lands on editing page that is disabled (cannot tap on to edit, no keyboard shows up and the 'Next' button is disabled.
- They can return to article page by tapping the 'x' button.
|Blocked editor decides to edit from article view||Block message shows over editor||Message dismissed by tapping 'OK' & editor lands on the editing page that is disabled|
Note for QA
As a part of this, please regression test page protection logic on our editor and article description editor, to be sure it still works as before. Our plan is to release blocked work, edit notices and abuse filter work before we pick up T313772.