-
Notifications
You must be signed in to change notification settings - Fork 17
Incorrect document element #8
Comments
I noticed this weirdness too but was hoping everything would just work... I guess not. Can you provide a minimal snippet of code that fails due to this so I can try a few things out? Thanks. |
Sure. Here's the snippet that tipped me off:
|
Strange thing is if I just do |
This also works:
(I am on version 0.9 which just got approved yesterday) |
oh now that is really weird :( oh wait, what version of Firefox are you on? Mac? |
Oooh, I do get that with Firefox 5... I was testing on Aurora... INTERESTING! |
I'm on Firefox 5.0.1, OS X. Aha! It doesn't happen on Aurora. Maybe it was an upstream problem? Ninja edit: you're too quick for me! |
I experimented a little but wasn't able to get the object out of the wrapper. I'll try to find help. |
It unwraps and exposes the real object var realObject= XPCNativeWrapper.unwrap(wrappedObject); |
Thanks @skarootz, I'll give that a try! |
@skarootz That doesn't seem to be working for me.
shows |
Not sure about the reason, I found that solution when I was trying to access On Fri, Jul 22, 2011 at 8:44 AM, rlr <
Jaime Hablutzel - 9-9956-3299 (tildes omitidas intencionalmente) |
Hi guys, I have found documentation about this on https://developer.mozilla.org/en/XPCNativeWrapper. Now, I got console.log working in a quick example, needs to be wrapped in a check of course
Hope we can narrow this down to a fix :) |
Yay, thanks @yvesvanbroekhoven! I think that fixes it ^^ |
While jumping between Chrome and Firefox I noticed that some custom JS scripts I run were not working correctly in Firefox.
Turns out the
document
element isn't actually a realdocument
object. Instead of returning the expectedHTMLDocument
object, it returns[object XrayWrapper [object HTMLDocument]]
.Is there any way to have
document
refer to the realHTMLDocument
object?The text was updated successfully, but these errors were encountered: