Closed
Bug 1254608
Opened 9 years ago
Closed 9 years ago
Complete the implementation of chrome.bookmarks.BookmarkTreeNodeUnmodifiable
Categories
(WebExtensions :: Untriaged, defect)
WebExtensions
Untriaged
Tracking
(Not tracked)
RESOLVED
WONTFIX
Iteration:
48.1 - Mar 21
People
(Reporter: bsilverberg, Assigned: bsilverberg)
References
(Blocks 1 open bug)
Details
This is listed as an outstanding item to implement to complete the implementation of chrome.bookmarks. It's documented at [1] and is listed as implemented in 45, but I think that's just because the scheme makes it look like it's been implemented.
[1] https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/bookmarks/BookmarkTreeNodeUnmodifiable
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → bob.silverberg
Status: NEW → ASSIGNED
Iteration: --- → 48.1 - Mar 21
Flags: blocking-webextensions+
Assignee | ||
Comment 1•9 years ago
|
||
Having opened this bug I'm not quite sure what, if anything, needs to be done to implement it. As far as I can tell, all existing bookmarks and folders, including the root folders, can be modified, and therefore would not include this attribute. Is the idea here to provide a mechanism for an API client to create a bookmark or folder that is not modifiable by a user, and then return that information via the API when that bookmarkNode is returned? That doesn't seem accurate because the create() method does not accept an argument for that.
What exactly is this to be used for, and what, if anything, do we need to do to implement it?
Comment 2•9 years ago
|
||
Yeah, we don't currently have unmodifiable bookmarks, so this isn't relevant.
Assignee | ||
Updated•9 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•