Closed
Bug 592925
Opened 14 years ago
Closed 14 years ago
Fix collection sharing API's understanding of writability
Categories
(addons.mozilla.org Graveyard :: Collections, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
5.11.9
People
(Reporter: fligtar, Assigned: jbalogh)
Details
(Whiteboard: [r])
Attachments
(1 file)
1.05 KB,
patch
|
fligtar
:
review+
|
Details | Diff | Splinter Review |
The Collector uses this list of collections for its purposes: https://preview.addons.mozilla.org/en-US/firefox/api/1.3/sharing Collections the user has write access to have writable="yes". Since new collections were born, collections that should have a yes have a no. This touches remora.
Reporter | ||
Updated•14 years ago
|
Whiteboard: [z] → [r]
Assignee | ||
Comment 1•14 years ago
|
||
Attachment #471398 -
Flags: review?(clouserw)
Reporter | ||
Comment 2•14 years ago
|
||
Comment on attachment 471398 [details] [diff] [review] look for zamboni's collection author (bug 592925) I tested this and it fixes the problem. Code looks good too. I'm still a module peer, damnit!
Attachment #471398 -
Flags: review?(clouserw) → review+
Assignee | ||
Comment 3•14 years ago
|
||
(In reply to comment #2) > I tested this and it fixes the problem. Code looks good too. I don't know about that, but thanks. r73722
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•