Bug 81342 - unable to download motorola phone user manual from commerce.motorola.com
Summary: unable to download motorola phone user manual from commerce.motorola.com
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: mozilla (Show other bugs)
(Show other bugs)
Version: phoebe
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Christopher Blizzard
QA Contact: Ben Levenson
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-01-08 10:13 UTC by Leonid Kanter
Modified: 2007-04-18 16:49 UTC (History)
1 user (show)

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: ---


Attachments (Terms of Use)

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.


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