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 14576 - Is WRONG_DOCUMENT_ERR historical?
Summary: Is WRONG_DOCUMENT_ERR historical?
Status: RESOLVED INVALID
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: DOM (show other bugs)
Version: unspecified
Hardware: All All
: P2 minor
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-27 19:50 UTC by Aryeh Gregor
Modified: 2011-10-27 20:05 UTC (History)
2 users (show)

See Also:

Attachments

Description Aryeh Gregor 2011-10-27 19:50:04 UTC 
The spec doesn't say to throw WRONG_DOCUMENT_ERR anywhere.  Should it be marked historical, or are there users in other specs?  APIs have mostly been updated to silently adopt nodes from the wrong document, so perhaps it's not needed anymore.
Comment 1 Aryeh Gregor 2011-10-27 20:05:31 UTC 
I was searching for WRONG_DOCUMENT_ERR instead of WrongDocumentError.  smaug____ points out that it actually is used, e.g., in isPointInRange().