Closed
Bug 984898
Opened 10 years ago
Closed 10 years ago
Places async transactions: Implement "new separator" ui command
Categories
(Firefox :: Bookmarks & History, defect)
Tracking
()
VERIFIED
FIXED
Firefox 31
People
(Reporter: asaf, Assigned: asaf)
References
Details
(Whiteboard: p=2 s=it-31c-30a-29b.2 [qa-])
Attachments
(1 file)
3.98 KB,
patch
|
mak
:
review+
|
Details | Diff | Splinter Review |
This is the easiest one, I think.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → mano
Blocks: fxdesktoptriage
Updated•10 years ago
|
Whiteboard: p=0
Updated•10 years ago
|
Status: NEW → ASSIGNED
Whiteboard: p=0 → p=2 s=it-31c-30a-29b.2
Comment 1•10 years ago
|
||
Hi Mano, can you explain this bug a little more? I'd like to figure out if we should be doing some QA to verify this once it's fixed, and if so, what it means and how to verify it. Thanks!
Flags: needinfo?(mano)
Whiteboard: p=2 s=it-31c-30a-29b.2 → p=2 s=it-31c-30a-29b.2 [qa?]
Updated•10 years ago
|
No longer blocks: fxdesktopbacklog
Flags: firefox-backlog+
Updated•10 years ago
|
Blocks: PlacesAsyncTransact
Assignee | ||
Comment 2•10 years ago
|
||
Hey Liz, This work as a whole can only be tested once it's completed (meaning that the QA should probably be done on the bug in which the feature will be turned on). The individual bugs may be used as hints for what needs to be tested (For example, here we're going to re-implement the New Separator command, accessible for places context menus and the places library). In the short term, no QA is necessary.
Flags: needinfo?(mano)
Assignee | ||
Comment 3•10 years ago
|
||
Attachment #8402606 -
Flags: review?(mak77)
Comment 4•10 years ago
|
||
Comment on attachment 8402606 [details] [diff] [review] patch.diff Review of attachment 8402606 [details] [diff] [review]: ----------------------------------------------------------------- Ok, but we need either a test or a test plan. ::: browser/components/places/content/controller.js @@ +282,5 @@ > case "placesCmd_new:livemark": > this.newItem("livemark"); > break; > case "placesCmd_new:separator": > + Task.spawn(this.newSeparator.bind(this)).then(null, Cu.reportError); I think all of this is not needed with Task.async, it's basically equivalent to calling a method that returns Task.spawn, with an already bound this and with the given argument. So here you should just be able to do this.newSeparator().then(null, Cu.reportError); @@ +789,5 @@ > + } > + > + let guid = yield PlacesTransactions.transact( > + PlacesTransactions.NewSeparator({ parentGUID: yield ip.promiseGUID() > + , index: ip.index })); nit: I'd prefer a temp var assignment to improve readability here. @@ +790,5 @@ > + > + let guid = yield PlacesTransactions.transact( > + PlacesTransactions.NewSeparator({ parentGUID: yield ip.promiseGUID() > + , index: ip.index })); > + let itemID = yield PlacesUtils.promiseItemID(guid); This should be itemId and promiseItemId (lowercase d)... there's no promiseItemID method, so this is broken. and this makes me think we probably want a new mochitests folder checking these commands do actually work...
Attachment #8402606 -
Flags: review?(mak77) → review+
Assignee | ||
Comment 5•10 years ago
|
||
It seems we don't have tests for places UI commands (that actually perform goDoCommand and so on). I'll file a bug for tests coverage.
Assignee | ||
Comment 6•10 years ago
|
||
https://hg.mozilla.org/integration/fx-team/rev/593d57a1e4c1
Target Milestone: --- → Firefox 31
Comment 7•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/593d57a1e4c1
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Tagged [qa-] based on comment 2.
Whiteboard: p=2 s=it-31c-30a-29b.2 [qa?] → p=2 s=it-31c-30a-29b.2 [qa-]
Updated•10 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•