Closed Bug 540843 Opened 13 years ago Closed 13 years ago
Do not cache dom element in ns
Object Frame shm code
No description provided.
Assignee: nobody → mozbugz
Attachment #422545 - Flags: review?(jst)
Having the nsObjectFrame own a content dom element is bad practice. We do not need to do that because we can cache the X window instead. This is basically what we were already doing inside of SetupXShm. The drawback is that once chrome calls SetAbsolutePosition, it can not change its mind with respect to what element the object element content is parented to. This is find, because that case was never suppose to work. (we had a runtime test to prevent that from happening).
Attachment #422545 - Flags: review?(jst) → review+
You need to log in before you can comment on or make changes to this bug.