21961 2008-10-29 16:20:26 -0700 for-in loops should not include undetectable properties (e.g. document.all) 2021-05-14 13:12:52 -0700 1 1 1 Unclassified WebKit DOM 525.x (Safari 3.1) PC OS X 10.5 RESOLVED WONTFIX http://code.google.com/p/chromium/issues/detail?id=3152 P2 Normal --- 1 jon webkit-unassigned arv ashvayka oldest_to_newest 97069 0 jon 2008-10-29 16:20:26 -0700 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> 97070 1 24761 jon 2008-10-29 16:21:15 -0700 Created attachment 24761 Test case 1760178 2 ashvayka 2021-05-14 13:12:52 -0700 (In reply to Jon@Chromium from comment #0) > Originated in Chromium bug tracker, see > http://code.google.com/p/chromium/issues/detail?id=3152 As it was concluded in Chromium bug tracker, `document.all` should be enumerable. [[IsHTMLDDA]] tries to fix web compatibility by introducing the minimum number of quirks necessary, thus keeping the ordinary value of [[Enumerable]]. This is tested by wpt/html/dom/idlharness.https.html (https://github.com/web-platform-tests/wpt/blob/afae1650e3441650024d04dc5837348ae3e0b049/resources/idlharness.js#L2903). 24761 2008-10-29 16:21:15 -0700 2008-10-29 16:21:15 -0700 Test case bug.html text/html 233 jon PGh0bWw+Cjxib2R5Pgo8c2NyaXB0Pgp2YXIgaGFzQWxsID0gZmFsc2U7CmZvciAocHJvcCBpbiBk b2N1bWVudCkgewogIGlmIChwcm9wID09ICdhbGwnKQogICAgaGFzQWxsID0gdHJ1ZTsKfQoKZG9j dW1lbnQuYm9keS5pbm5lckhUTUwgKz0gaGFzQWxsID8gIkZBSUxFRDogZGV0ZWN0ZWQgZG9jdW1l bnQuYWxsIHZpYSBmb3ItaW4gbG9vcCIgOiAiU1VDQ0VTUyI7Cjwvc2NyaXB0Pgo8L2JvZHk+Cjwv aHRtbD4=