Bug 574769 - Metric Display Range --> Advanced Settings + Internet Explorer = Error
Summary: Metric Display Range --> Advanced Settings + Internet Explorer = Error
Keywords:
Status: CLOSED DUPLICATE of bug 535772
Alias: None
Product: RHQ Project
Classification: Other
Component: Usability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks: rhq4 jon241-bugs
TreeView+ depends on / blocked
 
Reported: 2010-03-18 14:06 UTC by W. de Heiden
Modified: 2010-11-02 00:48 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-02 00:48:11 UTC
Embargoed:

Attachments (Terms of Use)
IE6 error when using Metric Display Range --> Advanced Settings (30.53 KB, image/jpeg)
2010-03-18 14:06 UTC, W. de Heiden 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 535772 0 low CLOSED Internet Explorer (IE) problem with Advanced Settings 2021-02-22 00:41:40 UTC

Description W. de Heiden 2010-03-18 14:06:37 UTC 
Created attachment 401026 [details]
IE6 error when using Metric Display Range --> Advanced Settings

Description of problem:

Using Jopr 2.3.1 With windows Internet Exporer gives an error when trying to set Metric Display Range --> Advanced Settings
Despite setting a date in the pop-up screen nothing happens but an error. (a scren print is enclosed)


How reproducible:
Everytime using Internet Explorer

Steps to Reproduce:
1. Go to Monitor. Try to set Metric Display Range --> Advanced Settings
2. Give start en end date and press OK
3. nothing happens but an error
  
Actual results:
nill

Expected results:
Metric display according to the dat set previously

Additional info:
Tested on Windows XP, Vista en Windows 2003 using IE6,7 and 8

Jopr Server 2.3.1 running Linux (RHEL 4.7)
Comment 1 Charles Crouch 2010-11-02 00:48:11 UTC 

*** This bug has been marked as a duplicate of bug 535772 ***
Note You need to log in before you can comment on or make changes to this bug.