This URI does not work here inasfar as that it does not navigate to the
section in question. The URI that does it is currently
<
https://dom.spec.whatwg.org/#dom-document-getelementsbytagname>
Your URI might have worked before just as mine does now, but that is
precisely the unreliable behavior that you can expect with a "Living
Standard", a resource that does not remotely meet the criteria for a
standard.
WHATWG HTML is not the normative resource; instead, it is
<
https://www.w3.org/TR/2015/REC-dom-20151119/#dom-document-getelementsbytagname>
as referred to by
<
https://www.w3.org/TR/2016/REC-html51-20161101/infrastructure.html#common-dom-interfaces> pp.
Although in both cases the return value is specified as an object that
implements the HTMLCollection interface, this is actually compatibly
implemented only as an object implementing the NodeList interface. By
contrast to an HTMLCollection, using the bracket property accessor syntax
with non-numeric string parameter, or calling the referred object’s
namedItem() method with an argument of that form, on the return value, does
not always yield useful results.
In any case, the problem with this approach is that one would have to
iterate over a lot of irrelevant elements as not all elements can have
values. If the question is understood literally, then “value” means the
“value” attribute, and not all elements have it.
In order to avoid this, there are several alternatives, including:
- calling document.getElementsByTagName() with a specific element type name
as argument, maybe several times, and if necessary, aggregate the results
in an array;
- calling document.querySelectorAll() as provided by implementing the
Selectors API with a CSS selector that includes all the relevant element
type names;
- calling document.evaluate() as provided by implementing DOM Level 3 XPath
to retrieve references to the relevant element objects and/or their
“values” directly (according to MDN, supported by all major browsers
except Internet Explorer).
However, the OP appears to have an X–Y problem; they appear to have the
misconception that they need to retrieve the values of all elements to
achieve their goal. That is not so.
For example, one can determine which elements the user has added by
observing mutations to the document tree:
<
https://developer.mozilla.org/en-US/docs/Web/API/MutationObserver>
Also, the original code is invalid HTML, and if that is corrected, it will
still not work as the function is being referred to, but not called.
--
PointedEars
FAQ: <
http://PointedEars.de/faq> | SVN: <
http://PointedEars.de/wsvn/>
Twitter: @PointedEars2 | ES Matrix: <
http://PointedEars.de/es-matrix>
Please do not cc me. / Bitte keine Kopien per E-Mail.