Closed
Bug 203060
Opened 21 years ago
Closed 21 years ago
Ebay "watch item" link causes browser to crash
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 195116
People
(Reporter: lutimdale, Assigned: asa)
References
()
Details
(Keywords: crash, stackwanted)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030422 Firebird™ Browser/0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030422 Firebird™ Browser/0.6 when going to an item detail, and clicking on "Watch this item" link, the browser crashes. This happens for a clean Mozilla 1.3 install and a Firebird_2002-04-22_nightly. Reproducible: Always Steps to Reproduce: 1. search item on ebay 2. view item detail 3. click on "watch this item" link 4. may have to login if not already logged in Actual Results: Browser crashes Expected Results: not crash, try to render the page as best as possible.
WFM Win2k 2003042208 Reporter: Please include a Talkback ID with your report if you do crash.
Reporter | ||
Comment 2•21 years ago
|
||
Not sure how I get the talkback ID. I did recreate the error and when talkback kicked in, I typed in some comments in the url/comments fields. Hope that helps.
Comment 3•21 years ago
|
||
I don't think Firebird has Talkback, can you try to reproduce this with a Mozilla nightly build and then submit crash data via the Netscape Feedback Agent, and post the associated Talkback ID using "mozilla\bin\components\talkback.exe" ?
Keywords: crash,
stackwanted
Comment 4•21 years ago
|
||
I don't know if this helps, but anyways: It's not reproduceable with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 -- Regards Marco
Comment 5•21 years ago
|
||
in the absence of further info, this sounds like a dupe of bug 195116 (related: bug 211735) *** This bug has been marked as a duplicate of 195116 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•