Bug 362006 - [api] Element.getAttributeNode will create an Attribute for implied values
Summary: [api] Element.getAttributeNode will create an Attribute for implied values
Status: RESOLVED FIXED
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: wst.xml (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.4 M3   Edit
Assignee: Nick Sandonato CLA
QA Contact: Nitin Dahyabhai CLA
URL:
Whiteboard:
Keywords: api, plan
Depends on:
Blocks:
 
Reported: 2011-10-25 16:50 EDT by Nick Sandonato CLA
Modified: 2011-11-09 17:16 EST (History)
1 user (show)

See Also:

Attachments
patch (1.96 KB, patch)
2011-10-25 16:52 EDT, Nick Sandonato CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Sandonato CLA 2011-10-25 16:50:29 EDT 
In the process of making sure implied values are returned for getAttribute, it looks like the functionality was carried over to getAttributeNode. The spec, however, reads that if the node by that name doesn't exist, null should be returned.

This will change getAttributeNode back to returning null even if a default value is suggested. getAttribute will continue to suggest the default value if the named attribute does not exist. To play it safe, and not break anyone in Indigo relying on this misbehavior, I'm targeting for Juno.
Comment 1 Nick Sandonato CLA 2011-10-25 16:52:44 EDT 
Created attachment 205951 [details]
patch
Comment 2 Nick Sandonato CLA 2011-10-25 16:56:27 EDT 
Code checked in.