Closed Bug 225170 Opened 22 years ago Closed 19 years ago

Crash when clicking on single arrow link at bottom of page

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: beckman, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 Firebird/0.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 Firebird/0.7 At the bottom of the URL at Wind River, there is a single arrow, pointing to the next page (to the right of the text that says "Page 1 of 4"). If you click on it, Firebird 0.7 crashes. The link goes to javascript:Tpage(0,1) Reproducible: Always Steps to Reproduce: 1. Go to http://www.windriver.com/products/index.html 2. Scroll to bottom of page. 3. Click on "|>" single "PLAY" next page image. Actual Results: Firebird crashed. Expected Results: Displayed the page after the javascript was executed.
Confirming on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031107 Firebird/0.7+ and Moz 2003102504. Not FB Specific. -> Browser - General I'll try to come up with a test case.
Status: UNCONFIRMED → NEW
Component: General → Browser-General
Ever confirmed: true
Product: Firebird → Browser
Version: unspecified → Trunk
Also confirming on a 2003-11-09 fb nightly and a 2003-10-28 seamonkey nightly on WinXP. Matti, can you reproduce this with a debug build and perhaps provide a stacktrace? If yes, can you please push it into the right category. I don't know if this is a layout or js issue.
Assignee: blake → general
QA Contact: general
It's dying in table_003.js, line 45. d.getElementById("Ttable"+id).innerHTML=s The problem doesn't occur off my computer though, so no testcase.
wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6a) Gecko/20031030
This same bug exists in Mozilla 1.6
Product: Browser → Seamonkey
Nothing to test - site has been redesigned, there is no arrow, next page or play to click Please reopen if you can provide a testcase for a current version of the suite.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.