Ya, an unfortunate side effect of using form.elements. The easy answer to this is "just don't use inputs named 'item'". Given that the fix is likely ugly, we haven't had anyone complain about this internally, and the work around is trivial, it's probably not worth the effort.

What we can do though is fail fast with a meaningful message (e.g., throw when elements returns a non-HTMLCollection or user passes the reserved names) or at the very least add a comment to the method. Just silently returning null now (which I assume is what it does) seems bad.

Feel free to re-open and/or send a PR with either of these and I'll review it.