Page MenuHomePhabricator

[Regression wmf20] Cursor traverses through the table unexpectedly with right/left arrow keys and throws following error in the console "Uncaught TypeError: Cannot read property 'start' of null"
Closed, ResolvedPublic1 Story Points

Description

Steps to reproduce:

1.Open a page with VE
2.Create a table
3.Now place your cursor inside last cell (4,4)
4.Press the right key three times , there will be an error in the console at this point ("Uncaught TypeError: Cannot read property 'start' of null")
6.Now press enter

Observed Result:
The cursor will jump to the second cell of first column (1,2)
Depending on how many times you pressed left key at step 4 , it jumps to different cell

See the screen capture

Event Timeline

Ryasmeen created this task.Mar 6 2015, 1:37 AM
Ryasmeen raised the priority of this task from to Needs Triage.
Ryasmeen updated the task description. (Show Details)
Ryasmeen added a project: VisualEditor.
Ryasmeen added a subscriber: Ryasmeen.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 6 2015, 1:37 AM
Ryasmeen renamed this task from [Regression wmf20] Cursor traverse through the table unexpectedly with right/left arrows and throws following error in the console "Uncaught TypeError: Cannot read property 'start' of null" to [Regression wmf20] Cursor traverses through the table unexpectedly with right/left arrow keys and throws following error in the console "Uncaught TypeError: Cannot read property 'start' of null".Mar 6 2015, 1:42 AM
Ryasmeen set Security to None.
Jdforrester-WMF triaged this task as Normal priority.
Jdforrester-WMF updated the task description. (Show Details)

Can't reproduce, possibly fixed by table selection patch recently merged.

Jdforrester-WMF moved this task from Nominated to Done on the VisualEditor 2014/15 Q3 blockers board.
Jdforrester-WMF moved this task from External and Administrivia to Q4 on the VisualEditor board.

yup the first time right clicking was selecting the cell previously and now its not doing that, and the issue is no more there now.
Checked the fix in Betalabs