The reason was that xpcnativewrappers was off by default to avoid such unsafe accesses. Setting xpcnativewrappers=no in chrome.manifest restored the FF 1.0.7 behavior.
- Godmar On 12/1/05, Neil <[EMAIL PROTECTED]> wrote: > Godmar Back wrote: > > >In FF 1.0, I was able to directly access javascript properties of the > >document shown in the appcontent window using > >event.explicitOriginalTarget.defaultView.document from inside a > >DOMContentLoaded callback. > > > >In FF 1.5, this seems to be the case no longer; or the DOMContentLoaded > >callback is invoked differently. For instance, when trying to access > >document.gs via event.explicitOriginalTarget.defaultView.document.gs on the > >Google result page I get a "no such property" exception, whereas the same > >code works in FF 1.0. > > > >Did anyone on this list encounter anything similar while transitioning to > >1.5? > > > > > I don't know if it's relevant but .defaultView and .document are > inverses - x.defaultView.document == x and w.document.defaultView == w > _______________________________________________ > Project_owners mailing list > [email protected] > http://mozdev.org/mailman/listinfo/project_owners > _______________________________________________ Project_owners mailing list [email protected] http://mozdev.org/mailman/listinfo/project_owners
