Page MenuHomePhabricator

Backspace across paragraphs is broken on mobile VE (Android Chrome)
Open, MediumPublic

Description

  1. On Android Chrome, edit an empty VE Standalone page (e.g. go to https://rawgit.com/wikimedia/VisualEditor/master/demos/ve/mobile.html#!pages/empty.html )
  2. Set "Show model" and "Update on changes".
  3. Press Enter. Observe there are two paragraphs (blank lines) in the DOM, the model has two empty paragraphs, and the selection is in the second paragraph (range 3-3).
  4. Press Backspace.

Expected behaviour: the second paragraph is removed from both the DOM and the model, and the selection moves into the first paragraph (range 1-1).

Actual behaviour: Nothing happens. On pressing Backspace a second time, the selection moves into the first paragraph (range 1-1) but the second paragraph remains (both in the DOM and the model).

Event Timeline

Hmm, looking at the Filibuster trace, it looks very much like the native backspace action leaves the DOM unchanged. Will investigate further.

matmarex renamed this task from Backspace across paragraphs is broken on mobile VE to Backspace across paragraphs is broken on mobile VE (Android Chrome).Dec 12 2018, 5:43 PM
JTannerWMF subscribed.

Looks like @dchan is investigating so moving this into the investigating column until its ready for action.

Removing task assignee due to inactivity, as this open task has been assigned for more than two years (see emails sent to assignee on May26 and Jun17, and T270544). Please assign this task to yourself again if you still realistically [plan to] work on this task - it would be very welcome!

(See https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup for tips how to best manage your individual work in Phabricator.)

Change 812093 had a related patch set uploaded (by TK-999; author: TK-999):

[VisualEditor/VisualEditor@master] [WIP] Resolve some out-of-sync issues on Android with Google Keyboard

https://gerrit.wikimedia.org/r/812093

Looks like the patch here got moved to T312558 and merged -- we might want to QA this issue specifically.