Open dankurka opened 9 years ago
I'm not seeing this in Showcase [1] so perhaps there's something different about the
example.
[1] http://samples.gwtproject.org/samples/Showcase/Showcase.html#!CwCellTree
(I also tested against trunk.)
Reported by skybrian@google.com
on 2014-09-24 22:40:46
I can not reproduce it in the online showcase too, but i have found a reliable way to
break this example [1].
In the NodeInfo inner Class change these lines for level 0 and level 1:
return new DefaultNodeInfo<Composer>(dataProvider, cell);
to
return new DefaultNodeInfo<Composer>(dataProvider, cell, selectionModel, null);
and change the declaration of the selectionModel more generic to make the compiler
happy
private final SingleSelectionModel<String> selectionModel = new SingleSelectionModel<String>();
to
private final SingleSelectionModel<Object> selectionModel = new SingleSelectionModel<Object>();
it doesnt matter if the KeyboardSeletionPolicy is ENABLED or BOUND_TO_SELECTION, but
its more easy to see with the last option.
Steps to reproduces:
ENABLED:
Click on "Beethoven", see you can freely move with the arrow keys
Click on "Concertos", now the yellow marking does not move as the tree lost focus
Same happens if you now click on "No. 1 - C"
Again: the focus is only lost if one comes from above.
BOUND_TO_SELECTION:
Click on "Beethoven" to give the Tree focus
Move down
Stuck on Concertos as focus is lost.
Same from level 1 to 2
[1] http://www.tutorialspoint.com/gwt/gwt_celltree_widget.htm
Reported by Singu.B
on 2014-09-25 11:15:29
Are there any news on this bug?
Reported by Singu.B
on 2014-10-17 09:13:14
There have been a couple of fixes to keyboard navigation in CellTree but I don't know
if it fixes the same thing.
Reported by skybrian@google.com
on 2014-10-17 15:49:41
As a few months have passed and I am still interested in seeing this bug fixed I request
hereby a status update.
Reported by Singu.B
on 2015-01-19 14:34:48
As far as I know, nobody is working on CellTree at the moment. We need a volunteer.
Reported by skybrian@google.com
on 2015-01-20 23:10:30
I submit a patch to fix this.
https://gwt-review.googlesource.com/#/c/13830/
The problem is that saveChildState() { ... savedView.ensureAnimationFrame().removeFromParent() ... } (line 408) fires blur events on chrome. This blurs events are usually ignored using isRefreshing=true but looks like replaceChildren has a bug and the saveChildState was outside the isRefreshing=true...false block (line 246). The similar method replaceAllChildren has its saveChildState call inside the isRefreshing=true...false block (line 211).
Originally reported on Google Code with ID 8911
Reported by
Singu.B
on 2014-09-23 15:05:57