Closed
Bug 214249
Opened 23 years ago
Closed 13 years ago
nsIFormSubmitObserver should not use nsIContent
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: bzbarsky, Unassigned)
Details
I was fixing up all this usage of nsIContent in code that has no business using
it (camino, toolkit, etc), and one culprit that stuck out was nsIFormSubmitObserver.
Imo we should make that a proper IDL interface, rename to nsIFormObserver (per
jst's suggestion), and pass in an nsIDOMNode, not an nsIContent.
Comment 1•20 years ago
|
||
Also it's inconvenient that it uses nsIDOMWindowInternal instead of the public, frozen nsIDOMWindow[2].
As to nsIContent, maybe it should use nsINode instead.
| Reporter | ||
Comment 2•20 years ago
|
||
Yeah, using nsIDOMWindow would be good. As for nsINode, it's the same as nsIContent for purposes of this code; I still think than nsIDOMNode is the way to go.
Comment 3•20 years ago
|
||
Right. I was under the mistaken illusion that nsINode was available to non-MOZILLA_INTERNAL_API code, which it is not.
| Reporter | ||
Comment 4•20 years ago
|
||
It might become that way, actually (due to such code using nsIDocument), but that define is just a linkage issue, not whether you _should_ be using the interface. You shouldn't be.
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•