symphonycms/symphony-2 — Issue #959: [2.3 beta] Selectable + Orderable conflicts
Author: eKoeS
Created: 2011-12-09 16:42:48+00:00
State: open
Labels: ux-ui

This one is an oldie but it's still present in the current `integration` branch: on tables that are both `selectable` and `orderable`, clicking on a row triggers `mousedown.orderable` first and `click.selectable` second. As a result, that same row changes its background-colour twice because the two CSS states (`ordering` and `selected`) have different styles.

A quick fix is to add a new class `moving` that only exists while the row is being dragged, then removing it when it's dropped. Perhaps it's not the most elegant fix in the world, but it's simple and effective (and works in my local branch).

This way, every time you click on a row only the `selected` style is applied. Then, as soon as the cursor starts moving, the `moving` styles overwrite the `selected` ones and the conflict is solved.

Any better ideas?