Closed Bug 510372 Opened 16 years ago Closed 7 years ago

Default Namespace is ignored when processing XML attributes.

Categories

(Tamarin Graveyard :: Virtual Machine, defect)

x86
All
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WONTFIX
Future

People

(Reporter: cpeyer, Unassigned)

Details

Steps to reproduce: 1. Create an application with the following snippet var message:XML = <Result offset="0" total="6" xmlns="http://whatever.com/"> </Result>; public function init():void{ var ns:Namespace = new Namespace('http://whatever.com/');; var noTotal:XMLList = message.@ns::total; trace(noTotal); var total:XMLList = message.@total; trace(total); } 2. Run the application Actual Results: [blank space] 6 Expected Results: 6 [blank space] Workaround (if any): do not use namespace when accessing attributes in the default namespace Transferred Comments: Chris Peyer - Thu Aug 13 16:30:07 PDT 2009 Verified bug. Attribute in default namespace and not defined namespace. Not 100% sure if this is a bug as the Essential AS 3.0 book states that "Once the default namespace has been established, all subsequently created elements (but NOT attributes) without an explicit namespace are automatically qualified by the default namespace. This bug transferred from: http://bugs.adobe.com/jira/browse/ASC-3743
Flags: in-testsuite?
Flags: flashplayer-qrb?
Priority: -- → P3
Target Milestone: --- → flash10.1
Flags: flashplayer-qrb? → flashplayer-qrb+
Any fix for this bug will likely need version-checking for backwards compatibility.
Flags: flashplayer-needsversioning+
Target Milestone: flash10.1 → Future
Priority: P3 → --
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.