Page MenuHomePhabricator

Can't make table cell selections in read mode (like in VE)
Closed, ResolvedPublic0 Estimated Story Points

Description

Highlighting cells in a table normally result in cells being highlighted row by row, with no possibility of highlighting a column. After having entered (and left) VE however it is now possible to select cells as desired.

Note that the unexpected behaviour is IMHO an improvement over the normal behaviour since it allows you to select by cells better and to copy their contents and past these elsewhere. Something you cannot do in either VE editing mode or in the normal view mode.

Screencast (ogv): F26987

To reproduce:

  1. Go to any page with a table (e.g. this)
  2. Attempt to highlight the middle column
  3. Go into editmode in VE
  4. Leave VE (by e.g. clicking View)
  5. Highlight the middle column

Event Timeline

Lokal_Profil raised the priority of this task from to Needs Triage.
Lokal_Profil updated the task description. (Show Details)
Lokal_Profil subscribed.

It sounds to me like you are reporting a feature as a bug...?
Also, is that really an ogg (audio) file or has Phabricator broken it while uploading?

Krenair set Security to None.
matmarex subscribed.

Also, is that really an ogg (audio) file or has Phabricator broken it while uploading?

It's an ogg video file, but Phabricator currently assumes that all ogg files are audio-only. There's a bug for this somewhere. You can download it from the file's page.

It sounds to me like you are reporting a feature as a bug...?

It's a bug in that it is unexpected and inconsistent behaviour (because the page reacts differently before and after editing it). The ideal solution (IMHO) would be to make this the standard behaviour.

So maybe I'm reporting that a bug should be a feature...?

Ryasmeen triaged this task as Medium priority.Jan 15 2015, 2:08 AM
Esanders claimed this task.
Esanders subscribed.

This is by design and very deliberate. We have no plans to change VE selection of cells, nor override the system default in read mode.

Esanders edited projects, added Web-Team-Backlog; removed VisualEditor-Tables, VisualEditor.

Re-assigning to reading-web. The request is to be able make cell selections in reading mode (presumable for copy-paste). Not sure if that is worth exploring though.

Esanders renamed this task from Highlighting table cells differ before and after entering VEedit to Can't make table cell selections in read mode (like in VE).Jan 31 2016, 3:08 PM

This is by design and very deliberate. We have no plans to change VE selection of cells, nor override the system default in read mode.

It is still unexpected behaviour that highlighting works differently before and after entering VE (see Task description). If it is really on purpose that you cannot select columns when in reading mode then clicking "view" should disable it again. (Although I'll admit that that is of lower priority.

Almost everything behaves differently in VE (links, images, templates etc). That is expected behaviour.

Almost everything behaves differently in VE (links, images, templates etc). That is expected behaviour.

But it should not continue to behave differently after pressing "View" again (exiting VE-mode).

dr0ptp4kt lowered the priority of this task from Medium to Low.Aug 5 2016, 4:49 PM
dr0ptp4kt subscribed.

I'm downgrading this to Low for the time being given the tone of the thread. Speaking from the Reading Web side of things, at the moment it's not well aligned with quarterly or annual objectives, plus it's unclear what the ideal behavior is here in the Vector skin. There's an argument to be made that users want to select specific text in a cell, although I imagine at times users also want to get the cells as cells. I don't frankly know if any change is worth it.

That said, I think the latest comment was about having consistent pre- and post-toolbar tab change behavior. I'm totally unsure of how easy or hard that is from a technical perspective. There's a fair amount of wizardry involved in editable DOMs.

Jdforrester-WMF subscribed.

Almost everything behaves differently in VE (links, images, templates etc). That is expected behaviour.

But it should not continue to behave differently after pressing "View" again (exiting VE-mode).

And it doesn't in testing in Firefox or Chrome on Mac or Linux. The video is (I'm pretty sure) because @Lokal_Profil must have been pressing Ctrl which triggers Firefox's alternate table selection system; it's nothing to do with VE. I'm re-closing this as Invalid, but have put that idea into T142234: Consider providing a table contents selection system in read mode that lets you copy parts of tables (e.g. the first three columns), over-riding default browser behaviour.

Lokal_Profil changed the task status from Invalid to Resolved.Aug 8 2016, 8:28 AM

Almost everything behaves differently in VE (links, images, templates etc). That is expected behaviour.

But it should not continue to behave differently after pressing "View" again (exiting VE-mode).

And it doesn't in testing in Firefox or Chrome on Mac or Linux. The video is (I'm pretty sure) because @Lokal_Profil must have been pressing Ctrl which triggers Firefox's alternate table selection system; it's nothing to do with VE. I'm re-closing this as Invalid, but have put that idea into T142234: Consider providing a table contents selection system in read mode that lets you copy parts of tables (e.g. the first three columns), over-riding default browser behaviour.

I didn't do the selection using Ctrl-key, had I done that then step 2 would have produced the same result (column selection only).

That said I now get the same behaviour at step 2 as step 5 (row by row selection) which means the bug (different behaviour when returning to view mode) has been resolved in the meantime.