Bugzilla – Full Text Bug Listing
| Summary: | Stacked View Tabs Become Inoperable in Chrome | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Austin Riddle <austin.riddle> | ||||
| Component: | Workbench | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | RESOLVED NOT_ECLIPSE | QA Contact: | |||||
| Severity: | critical | ||||||
| Priority: | P3 | CC: | ivan | ||||
| Version: | 1.2 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Another note: Sometimes "View 5" and "View 6" are not even able to be activated from the very start of the application, if they are stacked behind another view. I haven't seen this problem in the other browsers. I've checked this with Chrome 1.0.154.65 on Windows XP and the problem persist as you described. But with latest Chrome Beta 2.0.180.0 everything is working fine. In Google Chrome 1.0.154.65 qooxdoo "click" and "mousedown" events are not fired properly. Needs more investigation. I've reproduce it with Controls Demo -> CTabFolder tab too several times. As Google Chrome v2.0.172.28 is already released and this version does not suffer from this bug I suggest to close this bug as NOT_ECLIPSE. Following suggestion from comment #5. With Chomes' auto-update there shouldn't be much users that run into this problem. Please feel free to re-open if you disagree. I have tested in Chrome 2.0.172.28 and I can reproduce the same behavior. Try switching to a perspective with stacked views and click directly on an inactive stacked view. Hi Austin, I've double checked it again, but I can't reproduce it anymore with Google Chrome v2.0.172.28. With v1.0.154.65 it was reproducible 100%. I will try to develop another sample project to illustrate. OK, using the same sample project, all you have to do to reproduce the behavior is to click on 'View 6'. You will find that it will not activate. It works fine in IE and FF. Thanks. Austin, can you check it with latest beta too: http://dl.google.com/chrome/install/182.3/chrome_installer.exe ? Thanks. (In reply to comment #11) > Austin, can you check it with latest beta too: > http://dl.google.com/chrome/install/182.3/chrome_installer.exe ? Thanks. > Using 3.0.182.3, I cannot reproduce the problem (although some other strange things happen, which I attribute to being a beta). As the bug can't be reproduced any more with Chrome 3 and 4 I will close it as NOT_ECLIPSE. |
Created attachment 135993 [details] Sample project that can be used to elicit behavior Build ID: 1.2M6 Steps To Reproduce: 1. Run the provided project in Chrome (My version: 1.0.154.65). 2. Select an entry in the tree of the view labeled "View". 3. In the view labeled "View 2", directly select a different item (don't click on the tab) 4. Now try to click on the tab of "View 5". 5. The result is that "View 5" cannot be activated. More information: 1. I have found this problem intermittently, but the above steps seem to reproduce it reliably. It seems to only affect Chrome.