585552 - result of executed string is not in the same scope as the page's window

Status: RESOLVED DUPLICATE of bug 690529

(DevTools :: General, defect)

Description

[Julian Viereck]

Executing

    foo="bar";

in the WebConsole puts the "foo" object not on the window object of the current page but on the sandbox object used to execute the string.

Related bugs:
  bug 572953: Cu.evalInSandbox should not ignore wrappedJSObject
  bug 574033: HUD Console should evaluate commands in window scope

Comment 1

[David Dahl :ddahl]

i'm pretty sure this is a dupe of bug 572953

Comment 2

[Kevin Dangoor]

I'm okay with us keeping this bug open for now.

This bug is annoying and may throw some people off, but it's not actually a blocker because you can still explicitly put things into window scope:

window.foo = "bar";

It's interesting that you can look up names in window scope without typing "window." but to set them in window scope you need to actually say "window."

Comment 3

[David Dahl :ddahl]

This is a sandbox issue that we may have little control over. CCing mrbkap for guidance

Comment 4

[Kevin Dangoor]

There's more useful discussion in bug 690529.