"Exception / NS_ERROR_ILLEGAL_VALUE / nsIRDFService.GetResource / bookmarksMenu.js :: anonymous :: line 129", dropping on '(Empty)'

RESOLVED FIXED in seamonkey2.0

Status

SeaMonkey
Bookmarks & History
--
minor
RESOLVED FIXED
9 years ago
9 years ago

People

(Reporter: sgautherie, Assigned: neil@parkwaycc.co.uk)

Tracking

({fixed-seamonkey2.0, polish})

Trunk
seamonkey2.0
x86
Windows 2000
fixed-seamonkey2.0, polish
Bug Flags:
wanted-seamonkey2.0 +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

9 years ago
Bug 513275 comment 2:
{
From  Robert Kaiser   2009-08-28 13:13:26 PDT

When dropping on '(Empty)', I get the following in the error console:

Error: uncaught exception: [Exception... "Component returned failure code:
0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIRDFService.GetResource]"  nsresult:
"0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame ::
chrome://communicator/content/bookmarks/bookmarksMenu.js :: anonymous :: line
129"  data: no]
}

Bug 513275 comment 13:
{
From  neil@parkwaycc.co.uk   2009-09-19 10:18:31 PDT

drop on (Empty) should work like drop on parent.
}
Flags: wanted-seamonkey2.0?

Comment 1

9 years ago
This is wanted but we won't block SM2.0 on it.
Flags: wanted-seamonkey2.0? → wanted-seamonkey2.0+
(Assignee)

Comment 2

9 years ago
Created attachment 402077 [details] [diff] [review]
Possible patch

I tried and failed to stop empty menus from opening. :-(
I also tried and failed to highlight the menu when hovering the (Empty). :-(
But at least this patch allows drops into the open menu correctly.
Assignee: nobody → neil
Status: NEW → ASSIGNED
Attachment #402077 - Flags: review?(iann_bugzilla)

Updated

9 years ago
Attachment #402077 - Flags: review?(iann_bugzilla) → review+
(Assignee)

Comment 3

9 years ago
Pushed changeset d586340867d9 to comm-central.
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
(Reporter)

Updated

9 years ago
Keywords: fixed-seamonkey2.0
Target Milestone: --- → seamonkey2.0
You need to log in before you can comment on or make changes to this bug.