Talk:Moderator Tools/Content moderation on mobile web

About this board

Your skin is incompatible with VisualEditor.

1
Summary by CescoAiel

Opened in the wrong discussion, apologies!

CescoAiel (talkcontribs)

Your skin is incompatible with VisualEditor. See https://www.mediawiki.org/wiki/Extension:VisualEditor/Skin_requirements for the requirements.


Is there a way to fix this?

Is there a way to show categories?

1
Al12si (talkcontribs)

Timeless seems to have stopped working, so I’m now left with no usable themes other than this one (Vector 2022 is completely unusable on narrow screens), but I remember I chose Timeless because something’s wrong with this.

Now that I’m forced to use this one I remember what’s the problem: It doesn’t show categories so it’s useless. Is there a hidden option I can turn on to show categories?

Reply to "Is there a way to show categories?"

coordinates not showing

1
EnTerbury (talkcontribs)
Reply to "coordinates not showing"
95.26.26.34 (talkcontribs)

"{{Hidden|" area doesn't open related text when this wiki-template enabled.

95.26.26.34 (talkcontribs)

I mean "{{Hider| ... " area

Reply to "MinervaNeue template"
176.220.40.245 (talkcontribs)

How can I remove the site extension index.php? Help me

Reply to "İndex.php"

Increasing viewport width threshold

1
Abhidevananda (talkcontribs)

Hi all. I've recently updated my MW from 1.35.2 to 1.39.0 with the new MobileFrontend extension. Everything works as intended, but unfortunately the new mobile view (based on this skin) is not ideal for my wiki. When the infobox is floated to the right like a second column, both the main content and the infobox become too narrow to be serviceable. I am told that in Minerva, the infobox is on the very top for viewports up to 719px width. How can I increase that width to something much larger, e.g. 3000px? Thanks.

Reply to "Increasing viewport width threshold"

Message templates for mobile on talk page

3
Bluerasberry (talkcontribs)
Samwalton9 (WMF) (talkcontribs)

Thanks for the suggestion @Bluerasberry. Mobile talk pages are out of scope for our team because the Editing team is currently working on the Talk pages project which is now focusing on updating mobile talk pages. You'd be best off posting this request somewhere like Talk:Talk pages project/Mobile so that this use case can be considered for the in-progress redesign :)

Bluerasberry (talkcontribs)
Reply to "Message templates for mobile on talk page"
Samwalton9 (WMF) (talkcontribs)

Hi all, quick update! We've decided to start with working on the Overflow menu as our first project, so that we can enable all administrators to access Block, Protect, and Delete buttons. We're also considering making this menu visible to all users, so that buttons like Menu and Page Information are also available to any editor. We'd appreciate your thoughts about this menu on that project page.

Reply to "Overflow menu"
Alexis Jazz (talkcontribs)

Per your request at https://en.wikipedia.org/wiki/Special:Diff/1097046751

Admin tools are not really a "safer" place to start. Yes, less users are directly impacted, but those users have themselves a much greater impact. If admins accidentally delete the wrong page, or fail to delete a page, that's going to be disruptive.

I agree Special:Preferences is important and Special:MobileDiff is a nightmare that needs to end ASAP. (and AFAIK that's planned)

Editnotices wouldn't have been a super pressing issue, but it's been five years since this "temporary" measure and the market share for mobile has only grown since then.

Whatever resources are currently being poured into DiscussionTools should be reassigned, fix only breaking bugs and security issues as it's becoming quite clear to me that it's going to be replaced.

Samwalton9 (WMF) (talkcontribs)

Thanks @Alexis Jazz: !

I hear you on admin tools, though our work was limited in scope to making the links to those admin tools more accessible, so there wasn't much danger of accidentally breaking the tools themselves. You can read about that work at /Overflow menu.

MediaWiki is absolutely full of 'temporary' measures that have been that way for 5+ years and I agree it's frustrating. I spoke to the Editing team (who are working on Discussion Tools) and it looks like they might actually spend some time on editnotices sooner than our team would have got to it. There should be more info on that being posted on enwiki soon.

We're starting to think about Diff/MobileDiff and undoing edits while technical work on Preferences is underway (/Preferences). One thing that's been on my mind, that I'd love your thoughts on, is whether clicking Undo on mobile should always open the full editor. At the moment (with AMC turned on) that's what happens on mobile like on desktop, but in my experience as an editor/admin I rarely ever do a partial undo; it's much more likely that I just undo an entire edit. On desktop that's not too bothersome but on mobile it means a lot of scrolling before you find the save page button. Does that match your experience (on desktop or mobile), or do you find yourself using the edit window when undoing edits?

Alexis Jazz (talkcontribs)

"I spoke to the Editing team (who are working on Discussion Tools) and it looks like they might actually spend some time on editnotices sooner than our team would have got to it."

Does this mean editnotices in general, or editnotices in DiscussionTools? In case of the latter, I really don't believe they should bother. But if they could spare any resources at all, I could probably use them..

"Does that match your experience (on desktop or mobile), or do you find yourself using the edit window when undoing edits?"

I suppose this is partially why I request the rollback right on wikis where I edit a lot. Fire and forget, love it. When I undo, I actually do perform partial or altered undoes fairly often. Most of the time an undo is just an undo though. Occasionally I'll preview before publishing.

Perhaps the way the "thanks" link works could be a viable approach here? Silently check if the edit can be undone and give inline choices to instantly undo, open the full editor or cancel. To make it more responsive, show the text immediately with the instant undo link greyed out/disabled. Enable the instant undo link if the silent check comes back positive. When clicked, the instant undo should ask for an edit summary in a popup. This would be nice on desktop too!

And of course, preventDefault() and an href to undo in the full editor on the original link so especially desktop users can still quickly go there with a middle click.

Reply to "Priorities"

allow pending changes review

8
Johnnyconnorabc (talkcontribs)

On en.wp, pending changes can only be accepted but not reverted. If the 'revert' option is chosen, an error message will be displayed after entering an edit summary.

Samwalton9 (WMF) (talkcontribs)

Thanks for flagging this. I tried to revert a change on Special:PendingChanges from mobile and I'm actually struggling to even do so - where do you see the 'revert' option? If you have screenshots that would help me understand the problem.

Johnnyconnorabc (talkcontribs)
Johnnyconnorabc (talkcontribs)

Adding to my original comment, the pending changes review interface often simply fails to open, instead displaying a diff, as it (probably) did in your case. The interface is in desktop version and pending changes cannot be reverted even if it manages to open.

Johnnyconnorabc (talkcontribs)

Strange, though-the interface has failed to open at all today.

Samwalton9 (WMF) (talkcontribs)

Oh so you're trying to use Special:PendingChanges via the desktop interface, but on a mobile device?

Johnnyconnorabc (talkcontribs)

No. I meant that opening the diff via clicking (review) at Special:PendingChanges would open an unmodified desktop interface even if it was in mobile editing mode. Certainly a puzzling issue.

Samwalton9 (WMF) (talkcontribs)

Oh I see. Indeed - if you could send any screenshots or screen recordings that would really help me understand the issue :)

Reply to "allow pending changes review"
Return to "Moderator Tools/Content moderation on mobile web" page.