Closed
Bug 94201
Opened 25 years ago
Closed 25 years ago
New windows unsuable after visiting this URL
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jonas, Assigned: asa)
References
()
Details
Visit the Computer Sweden news site (eg.
http://computersweden.idg.se/text/010806-CS10) and then open up a new window
(eg. with Ctrl-N or "Open Link in New Window"). That results in a couple of new
errors in the JavaScript console but no content in the window. Hitting "Home"
results in "Error: BrowserHome is not defined" on the JS console. Windows that
where already open are unaffected but any new windows are disfunctional.
Comment 1•25 years ago
|
||
worksforme, build 2001-08-06-08....
Jonas, what build are you using?
Comment 2•25 years ago
|
||
Browser, not engine. Reassigning to Browser-General component.
Assignee: rogerl → asa
Component: Javascript Engine → Browser-General
QA Contact: pschwartau → doronr
Comment 3•25 years ago
|
||
Resolving as WORKSFORME.
Using Mozilla trunk binary 20010731xx Linux, I saw the bug.
The new window was black and unusable.
Using Mozilla trunk binary 20010806xx Linux, no problem at all.
jonas@init.se: can you try the site again with an up-to-date build?
If there is no longer any problem, please mark this bug "Verified".
Otherwise, you can reopen it - thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 4•25 years ago
|
||
Sorry, forgot to mention the build. I've seen this for a while now and I
download new builds daily. I started noticing this somewhere around the 0.9.3
release. Currently I'm on 2001080608 Linux tar-ball so I'll reopen the bug.
Could it matter if I used an installer build?
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 5•25 years ago
|
||
Yes, that could matter. Perhaps Boris and I do not have one of
the extra components you may have installed...
| Reporter | ||
Comment 6•25 years ago
|
||
Some more research shows that removing my prefs.js file resolves the problem.
Likewise, starting with a fresh ~/.mozilla/ and putting the old prefs.js in it
makes the problem reappear.
Having to nuke ones preferences (and saved passwords, cookie-settings etc.) is
annoying but there are better bugs to spend time on. This can't be a WORKSFORME
though as it is reproducable so I suggest marking it as WONTFIX.
Severity: normal → minor
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → WONTFIX
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•