Bug 1039476 - Strange behaviour when bringing tabbed panels forward in Safari & IE 11
Summary: Strange behaviour when bringing tabbed panels forward in Safari & IE 11
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: BAM
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER1
: 6.0.1
Assignee: David Gutierrez
QA Contact: Jan Hrcek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-09 08:59 UTC by Jan Hrcek
Modified: 2014-08-06 20:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
IE 11, Safari 5,6
Last Closed: 2014-08-06 20:04:08 UTC
Type: Bug


Attachments (Terms of Use)
Panel not loaded correctly (524.87 KB, image/png)
2013-12-09 08:59 UTC, Jan Hrcek
no flags Details
Steps to reproduce - video (6.33 MB, video/webm)
2013-12-09 09:01 UTC, Jan Hrcek
no flags Details
Javascript error captures in Safari in Mac (507.96 KB, image/png)
2014-01-23 10:59 UTC, Pedro Zapata
no flags Details
Javascript error captures in Safari in Mac (II) (497.02 KB, image/png)
2014-01-23 11:02 UTC, Pedro Zapata
no flags Details
Video showing steps to reproduce the issue on IE11 (1.80 MB, video/webm)
2014-01-29 11:43 UTC, Jan Hrcek
no flags Details

Description Jan Hrcek 2013-12-09 08:59:56 UTC
Created attachment 834231 [details]
Panel not loaded correctly

Description of problem:
When you have 'tabbed' panels on a page and you click the panel's tab header to bring the panel forward, the page is not updated correctly - instead only the panel's HTML is displayed (without the rest of the currently displayed page and without css styles). See screenshot (from Safari 6) and video (from Safari 5) of the problem

Version-Release number of selected component (if applicable):
This happens only in MAC OS X in Safari browsers. I tried on 2 different machines - one had Safari 5, the other had Safari 6 - the problem was the same in both.

How reproducible:
Always

Steps to Reproduce:
1. In dashbuilder go to Showcase, page By country (or any other page with 'tabbed' panels - i.e. panels in regions CENTER_3 or CENTER_6)
2. Click the headder of any of the tabbed panels to bring it forward

Actual results:
See videos - page not loaded fully with the panel activated, only the HTML contents of the panel are displayed.

When after the panel HTML is displayed, you click Back in the browser, then the page is fully displayed with the panel correctly activated.

Expected results:
Panel should be activated correctly just by clicking the 'tab header'.

Additional info:
there are no errors/exceptions in server.log

Comment 1 Jan Hrcek 2013-12-09 09:01:41 UTC
Created attachment 834232 [details]
Steps to reproduce - video

Comment 2 Pedro Zapata 2014-01-23 10:59:50 UTC
Created attachment 854304 [details]
Javascript error captures in Safari in Mac

Comment 3 Pedro Zapata 2014-01-23 11:02:17 UTC
Created attachment 854305 [details]
Javascript error captures in Safari in Mac (II)

Comment 4 Pedro Zapata 2014-01-23 11:03:17 UTC
Added screenshots with Javascript errors in Mac that need to be verified and fixed.

Comment 5 Jan Hrcek 2014-01-29 11:43:11 UTC
This bug is more serious than we initially thought, because it also manifests itself on Internet Explorer 11. Attaching video with current behavior in BPMS CR2 (reproduced on Windows 7) - see javascript errors in IE's javascript console below.

Comment 6 Jan Hrcek 2014-01-29 11:43:50 UTC
Created attachment 857017 [details]
Video showing steps to reproduce the issue on IE11

Comment 7 David Gutierrez 2014-01-29 17:07:58 UTC
Fixed.
This was an specific issue with the AJAX behaviour in some browsers (Safari, Konqueror, IE)


Github commit (master): https://github.com/droolsjbpm/dashboard-builder/commit/49993b0ab0a0a19683ee7d664480f500a1ce08c7

Github commit (6.0.x): https://github.com/droolsjbpm/dashboard-builder/commit/10ae850e4af2459501344a2f123c74c39c656115

Comment 8 Jan Hrcek 2014-02-20 06:01:55 UTC
Ok, verified with BPMS 6.0.1 ER1. Now it works correctly both in Safari and Internet Explorer.


Note You need to log in before you can comment on or make changes to this bug.