Invalid calling object (NodeList and Frames) - Bad var collection semantics for various objects (NodeList)

External Issue #110702

Details

Created
Apr 27, 2014
Privacy
This issue is public.
Found in build #
0.0010
Reports
Reported by 0 people

Sign in to watch or report this issue.

Steps to reproduce

URL = http://ie10bug.azurewebsites.net/root.aspx

URL:

Always Happens

REPRO STEPS:

I expect the NodeList to always be available since it’s held by a global object and the page has not been refreshed/reloaded.

EXPECTED RESULTS:

“Invalid calling object” error when F12 Developer Tools are displayed (in our production environment, the developer tools don’t need to be displayed to reproduce)

ACTUAL RESULTS:

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Justin R.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Justin R.” to “Li-Hsin H.”

      Changed Steps to Reproduce

      Changed Assigned To from “Li-Hsin H.” to “Riff J.”

      Changed Status from “Confirmed” to “In progress”

      Changed Status from “In progress” to “Won’t fix”

      Changed Status from “Won’t fix”

      Changed Assigned To from “Riff J.” to “Justin R.”

      Changed Status to “In progress”

      Changed Status from “In progress” to “Won’t fix”

      Changed Assigned To to “Justin R.”

      Changed Status from “Won’t fix”

      Changed Status to “Confirmed”

      Changed Assigned To from “Justin R.” to “IPBS P.”

      Changed Status from “Confirmed” to “External”

    You need to sign in to your Microsoft account to add a comment.

    Sign in