fwiw I've been asking MDN to standardise on "The path of the object from the global. If there isn't one, use the class name with the first upper-case part lower-cased" So, document.getElementById in this case.
-
-
-
I don't have the path information. I have the IDL interface name and the method name, and whether the method is static, that's it. (And note: the document might be an XHR responseXML or whatever, so `document` would be wrong in many cases anyway.)
- 6 more replies
New conversation -
-
-
Can the message use rich formatting? Using italics (<var>) could make element.querySelector clearer that element is a variable. It's also the convention the
@thedomstandard and@htmlstandard uses in their non-normative API boxes. https://dom.spec.whatwg.org/#ref-for-dom-parentnode-queryselector%E2%91%A0 … -
The message shows up in the devtools console, where maybe we could do that, but also shows up in the .message property of the exception, where having the <var> might be a bit weird...
- 1 more reply
New conversation -
-
-
Bring back DecompileValueGenerator
-
Let's not, please, especially because in cases when the method is being called via bind() and various such indirect things it wouldn't be able to produce anything useful anyway...
- 2 more replies
New conversation -
-
-
'getElementById requires... ' - why restrict to document?
-
Because you can have functions with the same name on different types of objects. For example, if `send() requires ...` it sure would be nice to know whether the `send` is on XHR, WebSocket, RTCDataChannel, PresentationConnection, or MIDIOutput.
- 2 more replies
New conversation -
-
-
Matching the other errors it would be: TypeError: Failed to execute 'getElementById' on 'Document': 1 argument required, but only 0 present.
-
Matching the what other errors? That specific "Failed to execute X on Y" style is only used by Chrome, and is explicitly _not_ something I want to emulate: it's too verbose and hides the actual error too much behind the wall of text at the front.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.