This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 258 - Entities and notations and NS methods
Summary: Entities and notations and NS methods
Status: RESOLVED FIXED
Alias: None
Product: DOM TS
Classification: Unclassified
Component: DOM Level 2 (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: Curt Arnold
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-29 18:27 UTC by Curt Arnold
Modified: 2003-11-27 00:20 UTC (History)
0 users

See Also:

Attachments
Eliminated use of getNamedItemNS to get entities and notations (9.33 KB, patch)
2003-11-26 19:19 UTC, Curt Arnold 		Details

Description Curt Arnold 2003-06-29 18:27:56 UTC 
From http://lists.w3.org/Archives/Public/www-dom-ts/2003Jun/0005.html


-- python stuff omitted --
Looking at CVS I see at least this one remains, in
namednodemapsetnameditemns10:

  <getNamedItemNS var="entity" obj="entities" namespaceURI="null"
  localName='"ent1"'/>
  ...same for notation...

Entities and notations shouldn't be gettable by NS methods as their
localNames are null. Hence the entity variable gets set to null, and an imp
is entitled to throw an implementation-dependant exception (re L1 SE 1.2)
instead of a HierarchyRequestErr.

I note the native-Java expressions seem to have gone, though, hurrah.

-- 
Andrew Clover
mailto:and@doxdesk.com
http://www.doxdesk.com/
Comment 1 Curt Arnold 2003-11-26 19:19:14 UTC 
Created attachment 69 [details]
Eliminated use of getNamedItemNS to get entities and notations
Comment 2 Curt Arnold 2003-11-26 19:20:54 UTC 
Per WG telecom 26 Nov 2003, eliminated use of getNamedItemNS to obtain entities
and notations in namednodemapsetnameditemns10.  Added getNamedItemNS03 and 04 to
test that notations and entities can not be retrieved using getNamedItemNS