-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mark 'name' and 'namedItem' methods of an HTMLCollection as non-enumerable #1172
Comments
I'm working on this |
Page for reproduce - http://start.att.net |
duplicate of #1141 |
I've reproduce an another problem: Uncaught TypeError: Illegal invocation
at ShadowUI.getRoot (http://localhost:1401/hammerhead.js:10511:59)
at Object.set (http://localhost:1401/hammerhead.js:2328:68)
at value (http://localhost:1401/hammerhead.js:2983:183)
.... |
The last problem is regression of #1150 |
Aftex fix regression, I've the origin problem.
The simple example to reproduce: <html>
<body>
<script></script>
<script>
var nodeList = document.getElementsByTagName('script');
// Without proxing these statements log the 'false' value
// With proxing - 'true'
console.log(nodeList.hasOwnProperty('item'));
console.log(nodeList.hasOwnProperty('namedItem'));
</script>
</body>
</html> To fix this issue need to move |
* fix regression of DevExpressgh-1150 (DevExpress#1172) * fix review's issues * fix review's issues
…ss#1141, close DevExpress#1172) (DevExpress#1183) * fix `Incorrect overriding of the NodeList collection` (close DevExpress#1141, close DevExpress#1172) * change a test logic
This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow. |
Based on
https://testcafe-discuss.devexpress.com/t/uncaught-typeerror-elm-getattribute-is-not-a-function/304
There are two extra methods
item
andnamedItem
in thefor ... in
loop.Check all errors on this site.
The text was updated successfully, but these errors were encountered: