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 17434 - Java Interface specification error.
Summary: Java Interface specification error.
Status: NEW
Alias: None
Product: DOM TS
Classification: Unclassified
Component: DOM Level 2 (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Philippe Le Hegaret
QA Contact:
URL: http://www.w3.org/TR/DOM-Level-2-View...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-07 09:31 UTC by Alexey Utkin
Modified: 2012-06-07 09:31 UTC (History)
1 user (show)

See Also:

Attachments

Description Alexey Utkin 2012-06-07 09:31:14 UTC 
There are two interfaces:
Interface AbstractView
Interface DocumentView 

They are reference to each other instead of getting access to the Document interface as it was suggested:
"It defines an attribute which [references the target document] of the AbstractView."
(cite from http://www.w3.org/TR/DOM-Level-2-Views/views.html)

That happens because of mistake: the AbstractView.getDocument() method should return the Document, not the DocumentView interface.
The error is in W3C spec. All browsers do it right, but FX Webnode cannot due to declared JDK interfaces.