Bug 1070121 - Console UI gets confused on quick interaction
Summary: Console UI gets confused on quick interaction
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: EAP 6.4.0
Assignee: Enrique Gonzalez Martinez
QA Contact: Pavel Jelinek
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-26 09:37 UTC by Petr Kremensky
Modified: 2015-09-17 09:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1006875
Environment:
Last Closed: 2015-09-16 11:13:43 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Petr Kremensky 2014-02-26 09:37:21 UTC 
This is back with EAP 6.3.0.DR1

+++ This bug was initially created as a clone of Bug #1006875 +++

if you start switching between top tabs in console quite quickly the whole UI gets confused and one of two things is going to follow

1) some tabs become dead (clicking on them won't switch the tab)
2) browser keeps switching  between some tabs infinite loop

--- Additional comment from JBoss JIRA Server on 2013-09-11 08:56:16 EDT ---

Harald Pehl <hpehl> updated the status of jira HAL-191 to Coding In Progress

--- Additional comment from JBoss JIRA Server on 2013-09-11 10:21:42 EDT ---

Harald Pehl <hpehl> updated the status of jira HAL-191 to Resolved

--- Additional comment from JBoss JIRA Server on 2013-09-11 10:21:42 EDT ---

Harald Pehl <hpehl> made a comment on jira HAL-191

Background: Wrong order of PlaceManager.unlock()

--- Additional comment from Jan Stefl on 2013-09-27 05:34:22 EDT ---

6.2.0-ER3 verified - PASSED (Chromium 25.0.1364.160)
Comment 1 Petr Kremensky 2014-03-06 08:08:54 UTC 
I was able to reproduce also in 6.3.0.DR2
Comment 2 Jakub Cechacek 2014-07-15 09:06:06 UTC 
Issue is still valid with EAP 6.3.0.er9 and seems to be FF specific.
Comment 3 Jakub Cechacek 2014-07-16 11:23:03 UTC 
Moving to 6.4 as the issue is still valid for 6.3
Note You need to log in before you can comment on or make changes to this bug.