Bug 162837 - xpath attribute::name processing broken
xpath attribute::name processing broken
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: libxml2 (Show other bugs)
4
All Linux
medium Severity high
: ---
: ---
Assigned To: Daniel Veillard
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-07-10 02:05 EDT by Ralf Corsepius
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version: 2.6.20
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-10-21 19:17:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ralf Corsepius 2005-07-10 02:05:27 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.7.8-2

Description of problem:
Given this document (test.xml):
<opt name="foo"/>

Trying to evaluate xpath child::opt/attribute::name 
with libxml-2.6.19 (FC4) fails to find the attribute:

# xmlint --shell test.xml
/ > xpath child::opt/attribute::name
Object is a Node Set :
Set contains 0 nodes:

With libxml-2.6.16 (FC3) the same succeeds:
# xmllint --shell test.xml
/ > xpath child::opt/attribute::name
Object is a Node Set :
Set contains 1 nodes:
1  ATTRIBUTE name
    TEXT
      content=foo

However, xpath child::opt/attribute::* with both versions succeeds.


Version-Release number of selected component (if applicable):
libxml2-2.6.19-1

How reproducible:
Always

Steps to Reproduce:
see above.

Actual Results:  see above.

Expected Results:  function.

Additional info:

C.f. http://bugzilla.gnome.org/show_bug.cgi?id=309864

This bug renders libxml2 unusable for development of applications I am working on.
Comment 1 Daniel Veillard 2005-07-10 03:54:08 EDT
yes known problem in 2.6.19 . Yse the compact syntax
  opt/@name 
in the meantime.

Daniel
Comment 2 Daniel Veillard 2005-10-21 19:17:29 EDT
Fixed in 2.6.20 and later in rawhide,

Daniel

Note You need to log in before you can comment on or make changes to this bug.