Closed
Bug 425726
Opened 17 years ago
Closed 15 years ago
Unified Queries are not yet implemented, but the idl is hiding the fact.
Categories
(Firefox :: Bookmarks & History, defect, P2)
Firefox
Bookmarks & History
Tracking
()
RESOLVED
FIXED
Firefox 3.7a1
Tracking | Status | |
---|---|---|
status1.9.2 | --- | beta1-fixed |
People
(Reporter: cmtalbert, Assigned: mak)
References
Details
Attachments
(1 file, 2 obsolete files)
(deleted),
patch
|
dietrich
:
review+
|
Details | Diff | Splinter Review |
When performing a unified query over a set of history and bookmarks, the returned resultNode object is not properly contructed. the hasChildren attribute is set to true, but when you attempt to access any of those children or if you even access childCount you get the following exception thrown:
Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsINavHistoryContainerResultNode.childCount]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: ../../../../_tests/xpcshell-simple/test_places/queries/test_onlybookmark-tags-unified.js :: run_test :: line 137" data: no]
I will attach a test for this behavior.
Basic STR:
1. Create a database with information in both history and bookmarks
2. Query for that with a UNIFIED query.
3. Loop through the ContainerResultNode object and display all the information you queried for.
== Expected ==
Proper ResultNode object returned
== Actual ==
ResultNode object that is returned seems mis-constructed.
This seems like a pretty serious flaw, nominating for blocking.
Flags: blocking-firefox3?
Priority: -- → P2
Target Milestone: --- → Firefox 3
Comment 3•17 years ago
|
||
not implemented. should not be exposed in the idl. was to support bug 378798, which is blocking-.
Blocks: 378798
Comment 4•17 years ago
|
||
This does not block the final release of Firefox 3.
Flags: blocking-firefox3? → blocking-firefox3-
(In reply to comment #3)
> not implemented. should not be exposed in the idl. was to support bug 378798,
> which is blocking-.
>
I saw that bug, but I read it as "unified queries are not going to be exposed in the UI". Sorry for duping it.
Can we use this bug to land a fix that comments out that part of the IDL?
The option is not used in any critical code:
http://mxr.mozilla.org/mozilla/search?string=QUERY_TYPE_UNIFIED
Updated•16 years ago
|
Target Milestone: Firefox 3 → ---
Assignee | ||
Updated•15 years ago
|
Summary: Unified Query does not create proper ResultNode object → Unified Queries are not yet implemented, but the idl is hiding the fact.
Assignee | ||
Comment 6•15 years ago
|
||
i just added 2 comments, to avoid idl and uuid changes.
LEt me know if you want to comment them out and update uuid instead.
Assignee: nobody → mak77
Attachment #312292 -
Attachment is obsolete: true
Attachment #312293 -
Attachment is obsolete: true
Status: NEW → ASSIGNED
Attachment #395687 -
Flags: review?(dietrich)
Comment 7•15 years ago
|
||
Comment on attachment 395687 [details] [diff] [review]
patch v1.0
hrm. yeah, better than breaking compat for this, r=me.
Attachment #395687 -
Flags: review?(dietrich) → review+
Assignee | ||
Comment 8•15 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3.7a1
Assignee | ||
Comment 9•15 years ago
|
||
status1.9.2:
--- → beta1-fixed
Comment 10•15 years ago
|
||
Bug 451915 - move Firefox/Places bugs to Firefox/Bookmarks and History. Remove all bugspam from this move by filtering for the string "places-to-b-and-h".
In Thunderbird 3.0b, you do that as follows:
Tools | Message Filters
Make sure the correct account is selected. Click "New"
Conditions: Body contains places-to-b-and-h
Change the action to "Delete Message".
Select "Manually Run" from the dropdown at the top.
Click OK.
Select the filter in the list, make sure "Inbox" is selected at the bottom, and click "Run Now". This should delete all the bugspam. You can then delete the filter.
Gerv
Component: Places → Bookmarks & History
QA Contact: places → bookmarks
You need to log in
before you can comment on or make changes to this bug.
Description
•