Closed
Bug 280277
Opened 20 years ago
Closed 11 years ago
Add a contentWindow attribute to HTMLObjectElement
Categories
(Core :: DOM: Core & HTML, enhancement)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 827158
People
(Reporter: jwatt, Unassigned)
Details
(Keywords: html5)
Attachments
(1 obsolete file)
We have added a contentWindow member to the DOM for HTML frames. It would be useful to do the same for the HTMLObjectElement interface.
Reporter | ||
Comment 1•20 years ago
|
||
jst, I know I said I would do this, but I didn't think it would take as long as I've spent on it so far. I've gotten stuck on every approach I've taken. The main reason for that is probably because I'm splashing about in code that I don't know. Anyway, here's what I think I'm doing right. If you could give me an idea of where to proceed from here I'd appreciate it.
Comment 2•20 years ago
|
||
For the time being, since the subdocument is loaded by the frame, you could get the primary frame, and then maybe add a method to some interface implemented by nsSubDocumentFrame to get the right contentWindow?
Reporter | ||
Comment 3•19 years ago
|
||
jst: what do you think about adding contentDocument and contentWindow to HTMLEmbedElement at the same time? If you think that's a good idea, can I add the necessary members to the frozen nsIDOMHTMLEmbedElement interface, or should I create an nsIDOMNSHTMLEmbedElement interface?
Status: NEW → ASSIGNED
Comment 4•19 years ago
|
||
Go for it, but add a new interface, don't change the frozen one.
Reporter | ||
Updated•17 years ago
|
Assignee: jwatt → general
Status: ASSIGNED → NEW
Updated•15 years ago
|
Assignee: general → nobody
QA Contact: ian → general
Comment 5•12 years ago
|
||
So, we don't do frozen interfaces anymore, so the attribute can just be added to the nsIDOMHTMLObjectElement interface. For the implementation, I think we can just get the nsIDocument like in nsHTMLObjectElement::GetContentDocument, and then get the window by calling GetWindow(). (Smarter people CC'd on this bug, please correct me if I'm wrong.)
Comment 6•12 years ago
|
||
You should probably do something more like nsGenericHTMLFrameElement::GetContentWindow (possibly reusing the "get stuff from the frameloader" code by refactoring that into a static method or a method on the frameloader).
Comment 7•12 years ago
|
||
Comment on attachment 172769 [details] [diff] [review] not sure where to go from here Most of this patch is no longer relevant with the more recent suggestions for how to implement this change.
Attachment #172769 -
Attachment is obsolete: true
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Updated•10 years ago
|
Whiteboard: [good first bug][mentor=Ms2ger] → [mentor=Ms2ger]
Updated•10 years ago
|
Whiteboard: [mentor=Ms2ger]
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
•