Community
Participate
Working Groups
Build Identifier: 1.4M6 After pressing escape key in Firefox (tested with 3.6.15 and 4.0), RAP seems to lose its ability to directly react on user commands. E.g. if you want to open a dialog afterwards, it doesn't show up. It will only show up if you make another GUI change like opening the menu or change the selection in a table. Reproducible: Always Steps to Reproduce: 1. Start Firefox and open you RAP application 2. Press escape 3. Do something that changes something on the GUI (e.g. let a dialog appear) 4. Nothing happens 5. Do something else (e.g. open the menu or change a selection in a table) 6. Dialog tried to open before will show up
I've tried to reproduce it with both Controls Demo and Workbench Demo without success. Could you check both demos too? Could you provide a self running snippet or steps to reproduce with one of these demos?
I can't reproduce this error with the demos - are they up to date (1.4M6)? RAP Demo (http://rap.eclipsesource.com/rapdemo/) seems to be of a previous release, at least it tells so. Will try to create a demo and upload it, but this will take some time...
Frank, I'm testing it against RAP from CVS HEAD. Controls Demo and Workbench Demo are from CVS too.
After way more testing I found out that it all relies on Comboboxes. The bug only occurs when you select an enabled Combobox and then press escape. Unfortunately I cannot reproduce this with the examples (yet).
Frank, any additional information on this?
Created attachment 192453 [details] Simple example to show the problem Quick and dirty example. Shows a countdown in the status bar. Countdown isn't updated after you press Escape when the combobox is selected.
Made a small example and found out that the problem only occurs when you have a thread that updates the UI. Therefore I took the countdown counter of our application and put it into the ApplicationActionBarAdvisior. I'm not sure if all of these threads inside the fillStatusLine method are necessary, but besides the combobox- problem in firefox there were no other side-effects yet.
Frank, I think that you ran into this bug 260117. Please reopen this bug if you don't think so. *** This bug has been marked as a duplicate of bug 260117 ***