Page MenuHomePhabricator

Issues with switching between wikitext editor and VE
Closed, ResolvedPublic

Description

On iPhone 6s (iOS 12, mobile Safari) click on the pencil icon to start editing.

(1) In the editing mode, the pencil icon will present two options - 'Visual editing' and 'Source editing'.

If an article is opened in VE, switch to 'Source editing'. Without making any edits, switch to VE again - the editing mode is ended - the article is displayed in Read mode. Clicking on the pencil button again won't have any effect. The page needs to be reloaded.

(2) The second issue involves interaction with 'Help Panel' .

  1. Click on the pencil button to start editing an article. Switch to wikitext editor.
  2. Click on the Help Panel and click in the field to type some text.
  3. Click 'Continue' and then click 'Back'. Without making any changes in the field close the form.

(Do not submit the question.)

  1. The wikitext editor mode will display the page without the editing toolbar.

IMG_6659.PNG (1×640 px, 135 KB)

  1. The page needs to be zoomed in to see the toolbar. Click to switch to VE - the menu looks jumbled.

IMG_6656 (1).PNG (1×640 px, 95 KB)

Event Timeline

Does the help panel part of this bug still happen, now that we've prevented iOS from zooming in on the question input when it's focused?

Yes, the issue in (2) is still happening. Step 4 in (2) is tricky to reproduce though.

It seems that T213338: Toggling from VE to source to VE in MobileFrontend breaks has more details on (1).

This comment was removed by kostajh.

I am able to reproduce the second issue on mediawiki.org by loading an article to edit, starting out in wiki text mode, then toggling to VE. Help panel is not enabled there so I think that’s a MobileFrontend bug.

Etonkovidova closed this task as Resolved.EditedJan 16 2019, 12:11 AM
Etonkovidova claimed this task.

Re-checked it after some fixes were done on https://phabricator.wikimedia.org/T212967 - (2) seems to be fixed. The issue with jumbled menu options is still present, but it has nothing to do with interacting with Help panel.
(1) is also fixed (at least the issue is not present anymore), I am closing the task as Resolved for now.