Closed
Bug 310343
Opened 19 years ago
Closed 13 years ago
AbstractView.prototype and DocumentView.prototype are undefined
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
INVALID
People
(Reporter: stryker330, Unassigned)
References
Details
Attachments
(1 file)
|
414 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20050928 Firefox/1.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20050928 Firefox/1.4 AbstractView.prototype and DocumentView.prototype are undefined. They shouldn't be. Reproducible: Always Steps to Reproduce:
|
||
Comment 1•19 years ago
|
||
Could you please provide some more information? A testcase maybe?
|
Reporter | |
Comment 2•19 years ago
|
||
Every W3C interface object should have a prototype object, which users can use to add new methods and properties.
|
||
Comment 3•18 years ago
|
||
That wouldn't work anyway, since the DOM uses multiple inheritance and prototype chains are ... well chains not trees. So I'm tempted to wontfix this, since I see no benefit to fixing it.
Component: DOM: Views and Formatting → DOM: CSS Object Model
QA Contact: ian → general
QA Contact: general → style-system
|
||
Comment 4•13 years ago
|
||
These interfaces don't exist anymore.
Assignee: general → nobody
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Component: DOM: CSS Object Model → DOM
OS: Windows XP → All
QA Contact: style-system → general
Hardware: x86 → All
Resolution: --- → INVALID
|
Assignee | |
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•