Summary | XPath parser is not namespace-aware |
Queue | gloox |
Queue Version | SVN |
Type | Bug |
State | Accepted |
Priority | 2. Medium |
Owners | js (at) camaya (dot) net |
Requester | euroelessar (at) gmail (dot) com |
Created | 10/25/2009 (4976 days ago) |
Due | |
Updated | 03/04/2010 (4846 days ago) |
Assigned | 10/25/2009 (4976 days ago) |
Resolved |
Assigned to Jakob Schröter
State ⇒ Accepted
Priority ⇒ 2. Medium
Priority ⇒ 1. Low
State ⇒ Assigned
Type ⇒ Bug
xpath implementation.
doesn't understand that this stanza has Capabilities SE at all, but
i.e. Psi's caps (which doesn't support new format yet) are recognized
well.
The trouble is in namespaces, your parser doesn't understand that
<caps:c .. > is the same as <c .. >
State ⇒ Assigned
Type ⇒ Enhancement
<http://xmpp.org/extensions/xep-0115.html#legacy>. Will set the type
to enhancement request.
State ⇒ Unconfirmed
Queue ⇒ gloox
Summary ⇒ Caps from GMail talk gadget
Type ⇒ Bug
Priority ⇒ 1. Low
<priority>0</priority>
<caps:c xmlns:caps='http://jabber.org/protocol/caps'
node='http://mail.google.com/xmpp/client/caps' ver='1.1' ext='pmuc-v1
sms-v1'/>
<status>some status text</status>
<show>dnd</show>
<x xmlns='vcard-temp:x:update'>
<photo>ebe9172b22422b9e57192c0123126fb99ada53d8</photo>
</x>
</presence>
gloox's Capabilities SE doesn't handle this capabilities from GMail
talk gadget, so my client doesn't know about it and client version
detection works wrong