Open Bug 454596 Opened 17 years ago Updated 3 years ago

Sqlite datasource is not loading in a tree with flags=dont-build-content and without an initial value in the datasources attribute

Categories

(Core :: XUL, defect)

x86
Linux
defect

Tracking

()

People

(Reporter: laurent, Unassigned)

Details

If we have a tree element with a template, with flags="dont-built-content" and datasources="" (or ="rdf:null"), and then if we set by javascript the datasources attribute with an URI of a valid sqlite database, the content of the tree is not displayed. Here is an example of a such tree, with a button to load the content : <tree flex="1" datasources="" ref="*" querytype="storage" id="mytree" flags="dont-build-content"> <treecols> <treecol id="id" primary="true" label="id" flex="1"/> <treecol id="label" label="label" flex="3"/> </treecols> <template> <query>select product_id, label, price, cat_id from products</query> <action> <treechildren> <treeitem uri="?"> <treerow> <treecell label="?product_id"/> <treecell label="?label"/> </treerow> </treeitem> </treechildren> </action> </template> </tree> <button label="change" oncommand="document.getElementById('mytree').setAttribute('datasources','chrome://extensiontest/content/tplstorage/tests.sqlite');" /> (you can use database provided from the attachment 286688 [details] of the bug 321172 to test this example) Actual results: when we click on the button, there is no content in the tree Expected results: when we click on the button, the list of products should be displayed in the tree. If we have an initial value in the datasources attribute (another database for example), it works except that we have to move the mouse over the tree in order to see the new content (problem of refresh ?). If we remove the flags attribute, it works well.
It seems the problem appears also when the datasource is an XML datasources. So I think the problem is on the support of the flags attribute.
Assignee: jag → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.