[Webkit-unassigned] [Bug 21961] New: for-in loops should not include undetectable properties (e.g. document.all)

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Oct 29 16:20:26 PDT 2008


https://bugs.webkit.org/show_bug.cgi?id=21961

           Summary: for-in loops should not include undetectable properties
                    (e.g. document.all)
           Product: WebKit
           Version: 525.x (Safari 3.1)
          Platform: PC
               URL: http://code.google.com/p/chromium/issues/detail?id=3152
        OS/Version: Mac OS X 10.5
            Status: NEW
          Keywords: InChromiumBugs
          Severity: Normal
          Priority: P2
         Component: HTML DOM
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: jon at chromium.org


Originated in Chromium bug tracker, see
http://code.google.com/p/chromium/issues/detail?id=3152

Firefox, which also has undetectable document.all does not put "all" in for-in
loops over the document, so this is really about being consistent with Firefox.

See the attached test case.

<html>
<body>
<script>
var hasAll = false;
for (prop in document) {
  if (prop == 'all')
    hasAll = true;
}

document.body.innerHTML += hasAll ? "FAILED: detected document.all via for-in
loop" : "SUCCESS";
</script>
</body>
</html>


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the webkit-unassigned mailing list