Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1056033

Summary: S-ramp-ui: IE11 only - can't display artifact's details
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Andrej Vano <avano>
Component: DT GovernanceAssignee: Eric Wittmann <eric.wittmann>
Status: CLOSED WORKSFORME QA Contact: Jiri Sedlacek <jsedlace>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: atangrin, brmeyer, kconner, oskutka, soa-p-jira
Target Milestone: CR1   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-18 14:04:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
blank page none

Description Andrej Vano 2014-01-21 12:45:18 UTC
Created attachment 853215 [details]
blank page

Description of problem:
IE11 shows just a blank page when trying to display artifact's details

The URL changes to something like that: http://localhost:8080/s-ramp-ui/#details;uuid=bbc4056b-0772-4091-a9df-4b0b53706492 and the page will be blank
(see screenshot)

Version-Release number of selected component (if applicable):
6.0.0.CR1

How reproducible: 100%


Steps to Reproduce:
1. add some artifacts
2. access srampui, go to manage artifacts
3. click on some artifact name to get into it's details
4. blank page in IE11, no problem in IE10

IE10 version: 10.0.9200.16750
IE11 version: 11.0.9600.16384

Actual results:


Expected results:


Additional info:

Comment 2 Andrej Vano 2014-01-22 08:08:00 UTC
If you manually refresh the page, you can see "Loading artifact, please wait..." that will never change

Comment 3 Eric Wittmann 2014-01-22 19:27:30 UTC
I can't reproduce this on any of the Windows machines or VMs I have access to.  I'll probably need to be granted access to the specific machine that is having issues.

Comment 4 Brett Meyer 2014-08-18 14:04:37 UTC
Simply closing this one -- it's out-of-date and Eric couldn't reproduce.