Closed
Bug 171720
Opened 23 years ago
Closed 23 years ago
Crash when clicking an imported bookmark with an anchor
Categories
(SeaMonkey :: Bookmarks & History, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: steve, Assigned: bugs)
References
()
Details
(Keywords: crash, stackwanted)
The above URL was in my bookmarks list (imported from Netscape 4.7). Try to
access it and browser blows up. After editing the URL in the "manage bookmarks"
window to remove the "#4.8" part and all is fine again.
Comment 1•23 years ago
|
||
Could you please provide your build id?
Comment 2•23 years ago
|
||
sorry, missed it in the summary - 1.2alpha.
Tweaking summary
adding keyword
Keywords: crash
Summary: 1.2alpha crashes if bookmark has a "#<name>" anchor mentioned → Crash when clicking an imported bookmark with an anchor
Updated•23 years ago
|
Severity: major → critical
Comment 3•23 years ago
|
||
worksforme with linux trunk build 20020929 and 1.2a
if you add the "#4.8" back, does it still crash? you might also try a clean profile
| Reporter | ||
Comment 4•23 years ago
|
||
Reply to Andrew: If you edit the "#4.8" back, it seems to be OK. Extra
information for the original report: when browser crashed it did so after
starting to display the top part of the page in question. It was if it tried to
skip to the anchor when it got as far as reading it, but something went wrong at
that point.
Comment 5•23 years ago
|
||
did you send in a talkback report for the crash? if so, could you add the
talkback ID here?
| Reporter | ||
Comment 6•23 years ago
|
||
It just crashed. No talkback windows were offered for me to fill in a report.
Arguably, that's a bug in its own right, surely? :-)
I do have a talkback-enabled build AFAIK. It is the vanilla linux/i686 offering
from the Mozilla download pages (with build ID: 2002091016).
Comment 7•23 years ago
|
||
can you try again with latest build ?
http://ftp.mozilla.org/pub/mozilla/nightly/latest
Keywords: stackwanted
Comment 8•23 years ago
|
||
Steven, can you reproduce this crash with the latest Mozilla release?
Comment 9•23 years ago
|
||
Resolving due to lack of response from reporter
please reopen if the problem persists with a new build of Mozilla.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•