[Greasemonkey] Re: Q: explicitOriginalTarget.defaultView.document in FF 1.5

[Godmar Back]

Turns out the answer is to set xpcnativewrappers=no in chrome.manifest
to reenable such unsafe accesses.

 - Godmar

On 11/30/05, Godmar Back <godmar at gmail.com> wrote:
> Hi,
>
> this question is only tangentially related to GM, however, I'm
> wondering if the GM developers encountered similar problems.
>
> 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.
>
> Although I understand that GM should never have a need to directly
> access objects in this way, I'm wondering if maybe someone on this
> list might have encountered something during the GM transition to 1.5
> that could explain this phenomenon.
>
> Thanks,
>
>  - Godmar
>