Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 81342

Summary: unable to download motorola phone user manual from commerce.motorola.com
Product: [Retired] Red Hat Public Beta Reporter: Leonid Kanter <leon>
Component: mozillaAssignee: Christopher Blizzard <blizzard>
Status: CLOSED NOTABUG QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: phoebeCC: ekanter
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-01-08 18:42:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Leonid Kanter 2003-01-08 10:13:59 UTC
Description of problem:

Mozilla is unable to download motorola phone user manual from commerce.motorola.com

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

mozilla-1.2.1-3

How reproducible:

always

Steps to Reproduce:
1. open http://commerce.motorola.com/consumer/QWhtml/manual.html
2. select category "Phones" in first combobox
3. Try to select Product from second combobox
    
Actual results:

drop-down list is empty

Expected results:

there must be list of available phone models

Additional info:

In Konqueror everything is Ok

Comment 1 Christopher Blizzard 2003-01-08 18:42:46 UTC
In one of the scripts that's included in that file there's a function called
Product().

http://commerce.motorola.com/consumer/QWhtml/manual.js

This includes the code:

if (navigator.appName=="Netscape")
{
  history.go(0);
}

which, according to bz, was to get around some bug on Netscape 4 on Windows. 
Also history.go(0) didn't reload the page.  In Mozilla's case it does reload the
page so the entire form is reset every time.

This is a problem with the site, not with Mozilla.