Page MenuHomePhabricator

Mobile source-code editor: "edit this page" link missing ("edit lead section" duplicated)
Closed, DuplicatePublicBUG REPORT

Description

open https://en.wikipedia.org/wiki/Wikipedia in a desktop computer.
notice the second "edit source" link (to the left of "View History") has a tooltip that says "edit this page".
clicking on that link shows the entire page's source code, down to categories at the bottom.

image.png (487×1 px, 71 KB)

now open https://en.m.wikipedia.org/wiki/Wikipedia (mobile version).
notice the second "edit source" link (to the right of "History") has a tooltip that says ""Edit the lead section of this page".
clicking on that link shows only the page lead's source code.

image.png (399×1 px, 50 KB)

so it's not possible to edit the full source code in the mobile version.
this prevents, for example, moving content across sections or changing the order of sections.

this problem occurs with both the web version and the android app.

a workaround in the web version in mobile devices is to ask for the desktop version.

user preferences:

  • Appearance: Skin: Vector 2022
  • Editing: "Use the wikitext mode inside the visual editor, instead of a different wikitext editor." enabled.

Event Timeline

@Fgnievinski I looked at the code responsible for this: includes/Menu/PageActions/ToolbarBuilder.php#209 and this behaviour seems intentional. However, I can't find any tickets in phabricator documenting this decision... I'll see if I can gain some more historical context around this.

[update]
Looking at the mobile site in archive.org, it looks like the main edit icon has been pointing to just the lead paragraph since at least 2016 :P

Screenshot 2023-07-20 at 1.44.39 PM.png (1×2 px, 831 KB)

I'm assuming that this was due to mobile phones not being equipped to handle large amounts of wikitext editing. Given how mobile devices have progressed since then, it seems reasonable to revisit this decision.

I think it's fair to say this is a duplicate of T203151? As far as I know this is entirely intentional behavior and is how it has behaved since MobileFrontend's launch -- see @Jdlrobson's comment on T196915#4272716.