Created attachment 312292 [details]
Specific test for this issue
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.
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.
Created attachment 312293 [details]
header file for test
This seems like a pretty serious flaw, nominating for blocking.
not implemented. should not be exposed in the idl. was to support bug 378798, which is blocking-.
This does not block the final release of Firefox 3.
(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:
Created attachment 395687 [details] [diff] [review]
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.
Comment on attachment 395687 [details] [diff] [review]
hrm. yeah, better than breaking compat for this, r=me.
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.
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.