You're right. I just added a brief notice to the class comment.
Andreas G. schrieb:
> actually its quite logical ( now :) ) ... you only select nodes in the
> document instead of fetching them. i think that should be mentioned in the
> api.
>
> regards
>
>
>
> Daniel Wagner wrote:
>> Hi again,
actually its quite logical ( now :) ) ... you only select nodes in the
document instead of fetching them. i think that should be mentioned in the
api.
regards
Daniel Wagner wrote:
>
> Hi again,
>
> after a little consideration, I have to retract my previous statement:
> xml.Element.selectNo
Hi again,
after a little consideration, I have to retract my previous statement:
xml.Element.selectNodes() works as it should ;-)
If you pass in a *node* as the first parameter, the double slashes in
the XPath mean "search the entire document this node came from".
selectNodes() is a wrapper fo
thank you, that was the pitfall. how can i submit this bug?
Daniel Wagner wrote:
>
> Hi,
>
> I just managed to reproduce your problem and it looks like selectNodes()
> ignores the parent element if you use the double slashes and just
> interprets them in the standard XPath way, i.e. by sear
Hi,
I just managed to reproduce your problem and it looks like selectNodes()
ignores the parent element if you use the double slashes and just
interprets them in the standard XPath way, i.e. by searching the entire
document. I'll have to take a closer look at the xml.Element class, but
it sure
forgot to mention that "alert( qx.xml.Element.getSingleNodeText( items[2],
"//MenuTab[3]" ) )" works.
this is from the api: selectNodes((Element | Document) element, String
query) <- the first arg. must be an element or a document. i pass an element
to selectNodes but there goes something wrong.
hello again. new topic now. :)
my code:
var doc = qx.xml.Document.fromString( result );
var items = qx.xml.Element.selectNodes( doc, "//MenuItem" );
var tabs = qx.xml.Element.selectNodes( items[2], "//MenuTab" );
alert(tabs.length);
explanation:
the items array has 8 elements an
