- From: Dima Voytenko <notifications@github.com>
- Date: Wed, 21 Dec 2016 13:06:28 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 21 December 2016 21:07:11 UTC
The problem involves how HTML FORM inputs are exposed on the parent `<form>` element. It was originally introduced in the MS Internet Explorer as far back as JavaScript 1.0 and eventually copied by most of browsers. W3C DOM Level 2 spec has addressed this by introducing HTMLFormElement.elements collection. Unfortunately, the old behavior was left intact for backward compatibility. You can read more about this problem in this post: http://stackoverflow.com/questions/9158238/why-js-function-name-conflicts-with-element-id/9160009#9160009: One quote from this post: > As a result, the convenience feature introduced in JavaScriptâ„¢ 16 years ago still bites you like a bug in client-side DOM scripting today. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/388
Received on Wednesday, 21 December 2016 21:07:11 UTC