Greetings,
I have encountered a bug in the Edge browser's Javascript implementation of window.open(). The bug is present in 10240 and 10568.104. When the 'open' function is called, there should be an object returned that is the newly opened window. Inspecting or hovering over the returned object from within the Debugger should reveal all of it's publicly available functions and properties.
When I hover, I am only seeing the message:
* popup [object]
When I type the name of the variable containing the returned object into the Console, the following happens:
* Nothing for 20 seconds, then I get:
> [object Object] {applicationCach: Object{...}, blur: [object {...}, .. etc
At this point I can expand the arrow and see the publicly exposed functions and properties.
But then, if I go back to the Debugger and hover I only see "popup [object]".
Specifically, I am testing for the existence of the 'postMessage' member after the call to window.open() and receiving this error message:
SCRIPT449: Argument not optional
Calling Window.open does in fact generate a new window. But, using the developer tools from within the newly opened window is next to impossible. At first, clicking any of the tabs does nothing. It takes a good 20 seconds before I can use the console. Interrogating the window.opener property takes roughly 20 seconds for the object to appear in the console window. Trying to access the postMessage function from Javascript within the newly opened window results in an exception.
Window.open cats normally and as expected with all other OS / browser combinations.
Do you have any information about this bug, and when or if a fix for it might be available?
Kind regards,
-Greg