Closed
Bug 224050
Opened 21 years ago
Closed 21 years ago
crash on loading the KlipArt website
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: bulk, Assigned: bugzilla)
References
()
Details
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.1; Linux; en_GB, en)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007 Firebird/0.7 StumbleUpon/1.89
If I go to the URL http://users.skynet.be/kborrey/klipart/klipart.html then Firebird crashes
immediately without any error message or warning
Reproducible: Always
Steps to Reproduce:
1. In the URL bar enter http://users.skynet.be/kborrey/klipart/klipart.html
2. Click "Go"
3.
Actual Results:
abnormal termination of Firebird
Expected Results:
Load the website
Konqueror gives me a message telling me I've no plugin for SVG, so it may be an SVG related
bug
Comment 1•21 years ago
|
||
David, this works for me using a 2003-10-27 build on WinXP. A dialog comes up,
that I need the SVG-plugin and after I dismiss that the page comes up fine.
Please try again with a current nightly build from
ftp.mozilla.org/pub/mozilla.org/firebird/nightly/latest-trunk/ with a fresh
profile and without any additional themes and extensions. It may be that the
StumbleUpon extension you're using is responsible for this, since this extension
is very often related to crashes.
QA Contact: bugzilla
Reporter | ||
Comment 2•21 years ago
|
||
Tested now both with latest trunk and latest-0.7 and it works fine with both. Sorry for not trying
this before and wasting your time.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Comment 3•21 years ago
|
||
Reopening, because the correct resolution for this is WORKSFORME. Please only
use FIXED if you point your issue to a checkin.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Comment 4•21 years ago
|
||
Marking WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago → 21 years ago
Resolution: --- → WORKSFORME
Updated•19 years ago
|
QA Contact: bugzilla → general
You need to log in
before you can comment on or make changes to this bug.
Description
•