Closed dankurka closed 9 years ago
Workaround:
I could solve a lot of the issues above by overriding getConsumedEvents of "DatePickerCell"
as follows:
Set<String> s = new LinkedHashSet<String>();
s.addAll(super.getConsumedEvents());
s.add("focus")
return Collections.unmodifiableSet(s);
Seems like the "focus" event is missing in the DatePickerCell, which is a bit strange
given that it explicitly fires a focus event after it closes. Without this event, the
CellTable will never its isCellEditing state again, since the DatePickerCell won't
consume the focus event.
FURTHER NOTE:
This bugs should affect only tables which contain one or more readonly-columns!
It won't have an effect if all columns are writeable, as writeable columns affect the
edit state automatically. Maybe thats the reason why it wasn't reported before.
Reported by webmaster@hwsc.net
on 2011-06-20 16:31:48
Still exists in 2.5.0. The workaround helps a bit but there are other issues of selection
blocking:
1) when user cancels the date selection by clicking anywhere outside of picker;
2) when user changes the date in not selected row it gets selected but even after choosing
the date the selection is locked.
And yes, I have readonly columns in my CellTable.
Reported by radioanonzoi
on 2012-12-11 09:27:01
Reported by dankurka@google.com
on 2013-05-28 00:54:33
AssumedStale
Originally reported on Google Code with ID 6499
Reported by
Eric6iese
on 2011-06-20 16:10:35