Am 08.06.2016 um 18:48 schrieb Joe Medley:
). I think this is an excellent move. I have to confess that I haven't paid as much attention to error messages as I should, but I will start doing so in my MDN work.
Thanks and great! Happy to get some help with this!
> What concerns me is that there are no standards documented for how to do this, or at least none that I can find.
> I can start this discussion with a few observations.
> * First, the fact that there were specific pages for error types completely escaped my notice.
It is a brand new project that I only started to work on in the last few
weeks on MDN (after finishing the giant WebGL reference btw).
The error reference we are talking about in the Hacks article is only
for ECMAScript errors for now. Also it is much more granular than just
"MediaError" or in ECMAScript's case "TypeError", "SyntaxError" etc.
The errors that deserve their own pages are instances of these types of
errors. Here are lists of these for ECMAScript in some engines:
The idea is to create a page for each of those messages, and then link
them from the console. If the engines throw different messages, I am
mentioning both in one article, see e.g.
> * I've seen interface member pages that list errors thrown by that member. I couldn't find an example, but it seems they typically reside right after the syntax, whether as a subheading or as the next sibling, I don't remember.
In the WebGL reference, for instance.
Per the style guide we agreed on "Errors thrown" in the syntax section.
> The question is, how exactly should errors be documented on MDN? I'll be happy to help document the answer.
I haven't had the time so far, but as I want to grow the amount of error
pages, I will be happily writing a doc on how to get this done!
> dev-mdc mailing list
> MDN contributor guide: http://bit.ly/ContributorGuide
> Doc project Trello board: https://trello.com/b/HAhl54zz/status