Closed GoogleCodeExporter closed 8 years ago
That's ugly!
On checking, it appears to be related to the fact that Vaadin is misdirecting
user input like the ENTER key when multiple tabs are open. We can reproduce
the error you see when we have other tabs opened, as it seems the "default" key
on those tabs is firing when ENTER is pressed. But if we close those other
tabs so we just have the library open, then the ENTER key works as expected.
Original comment by yoz...@gmail.com
on 13 Oct 2013 at 6:14
Currently tracking this via the Vaadin forum:
https://vaadin.com/forum#!/thread/4122130
Original comment by yoz...@gmail.com
on 13 Oct 2013 at 6:32
Appears to also be tracked on Vaadin ticket 12743:
http://dev.vaadin.com/ticket/12743
Original comment by yoz...@gmail.com
on 13 Oct 2013 at 7:11
Please give this a check on the patch 1013 release we just installed. We
basically removed all of the default ENTER key logic for buttons.
Original comment by yoz...@gmail.com
on 13 Oct 2013 at 8:49
We're going to close this for now until such time as we attempt to re-introduce
default keys if Vaadin can resolve this capability that seems to misroute now.
In the 13.11.9 release, all such default keys should be deactivated.
Original comment by yoz...@gmail.com
on 11 Nov 2013 at 6:32
Original issue reported on code.google.com by
lstro...@gmail.com
on 13 Oct 2013 at 3:47Attachments: