At 11:54 AM 4/27/2005 -0400, Benoit Bezaire wrote:
Wednesday, April 27, 2005, 10:09:58 AM, Lofton wrote:
LH> Hi WebCGM TC,
LH> I'm working on the DOM test case for ApsAttr 'viewcontext', and think
LH> we ought to clarify something about the 'get...' methods. Specifically
LH> working with getAppStructureAttr, section 5.7.6 (but this probably
LH> somewhere else as well).
LH> Let's consider the case of 'viewcontext' first. Section 184.108.40.206 says
LH> "Initial value: none", which is reasonable. If I getAppStructureAttr on
LH> APS where there is no explicit 'viewcontext' ApsAttr, then the answer
LH> should be "undefined" (see side-issue about "undefined" below). This is
LH> the way DOM2 works, so we should stick with that unless we have a
LH> compelling reason to deviate.
I've been doing a bit more research on this... All DOM Level 1, 2 and
3 are very clear about the getAttribute() method (similar to
getAppStructureAttr), they all state that the return value is a
DOMString or an empty string if the attribute is not specified or
doesn't have a default (i.e., DTD) value.
Right. The only issue is whether or not the WebCGM-specific "Initial value"
concept is equivalent to "default (i.e., DTD)" value. We agree that it is
Could you send us a pointer to the DOM 'undefined' concept?
Indeed, if I had looked further on p.54, getAttribute method, return value
should be empty string as you said: "...value as a string, or the empty string
if that attribute does not have a specified or default value." So my
side-issue goes away, thanks.