Closed
Bug 104363
Opened 24 years ago
Closed 15 years ago
javascript error in bookmarksOverlay.js
Categories
(SeaMonkey :: Bookmarks & History, defect, P5)
Tracking
(Not tracked)
RESOLVED
EXPIRED
Future
People
(Reporter: bugzilla, Unassigned)
Details
1. go tohttp://gemal.dk/test/2.html
2. right click on the link there and say "open in new tab"
3. then you get en error saying that the page could not be loaded.
4. select the tab with the page the didn't load
5. press Bookmark -> Add bookmark
Error: aDocShell.currentURI has no properties
Source File: chrome://communicator/content/bookmarks/bookmarksOverlay.js
Line: 841
build 20011011
Updated•24 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Comment 1•24 years ago
|
||
Paul Chen is now taking Bookmarks bugs. For your convenience, you can filter
email notifications caused by this by searching for 'ilikegoats'.
Assignee: ben → pchen
Status: ASSIGNED → NEW
Mass move Ben's bugs dumped on me marked future with p5 to get off my untriaged
radar. You can filter out this email by looking for "ironstomachaussie"
Priority: -- → P5
| Reporter | ||
Comment 4•24 years ago
|
||
related to bug 104361
The error is now:
Error: aDocShell.currentURI has no properties
Source File: chrome://communicator/content/bookmarks/bookmarksOverlay.js
Line: 868
20020117
Comment 5•23 years ago
|
||
I am not seeing either of these errors on 20021115
Updated•21 years ago
|
Product: Browser → Seamonkey
Updated•18 years ago
|
Assignee: bugs → nobody
QA Contact: claudius → bookmarks
Comment 6•16 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 7•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•