Item5715: EditRowPlugin row edit focus gets confused with TablePlugin initsort

When you have an EditRowPlugin combined with a TablePlugin initsort, the focus does not work. The row becomes editable, but goes back to row's unsorted original position, and the focus does not jump to it - note that the table stays sorted - which leaves the users hunting for where the row edit went, especially on large tables.

%TABLE{initsort="2" sort="on"}%

%EDITTABLE{ header="on" format="|text|text|text|text|text|text|text|text|" headerrows="1" changerows="on" }% 

Example at: http://twiki.wrs.com/do/view/Sandbox/PaulineCheung

-- TWiki:Main/PaulineCheung - 18 Jun 2008

Tricky. The separation between the TABLE macro and the EDITTABLE macro means that the EditRowPlugin would have to parse the TABLE tag to determine that an initsort applied.

I don't think this can be fixed until we have a canonical table model to work from that is used by both plugins.

-- CrawfordCurrie - 15 Feb 2009

If pure JS editing is used, this is no longer a problem, so I'm closing it.

-- CrawfordCurrie - 14 Feb 2011

Re-opening because I added the option to put the control buttons at the end of a row.

-- CrawfordCurrie - 17 Feb 2011