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 17881 - Function declaration of Node::lookupPrefix and Node::lookupNamespaceURI do not allow 'null' return value
Summary: Function declaration of Node::lookupPrefix and Node::lookupNamespaceURI do no...
Status: RESOLVED DUPLICATE of bug 17570
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 07:11 UTC by contributor
Modified: 2012-08-27 08:45 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2012-07-18 07:11:21 UTC 
This was was cloned from bug 17570 as part of operation convergence.
Originally filed: 2012-06-22 01:46:00 +0000
Original reporter: svitlant@microsoft.com

================================================================================
 #0   svitlant@microsoft.com                          2012-06-22 01:46:59 +0000 
--------------------------------------------------------------------------------
Implementation details of Node::lookupPrefix (http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#dom-node-lookupprefix) and Node::lookupNamespaceURI (http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#dom-node-lookupnamespaceuri) functions indicate that the value 'null' can be returned. However, the declaration of those functions in Node interface (http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#node) does not have a question mark ('?') next to the return type of those functions.
================================================================================
Comment 1 Anne 2012-08-27 08:45:16 UTC 

*** This bug has been marked as a duplicate of bug 17570 ***