Document Object Model

We are committed to providing a friendly, safe, and welcoming environment for all. Please read and respect the Code of Conduct. Folks notice minor and larger issues with the DOM Standard all the time and we'd love your help fixing those. Pull requests for typographical and grammar errors are also most welcome. Issues labeled "good first issue" are a good place to get a taste for editing the DOM Standard. Note that we don't assign issues and there's no reason to ask for availability either, just provide a pull request. If you are thinking of suggesting a new feature, read through the FAQ and Working Mode documents to get yourself familiarized with the process. In short, change dom.bs and submit your patch, with a good commit message. Please add your name to the Acknowledgments section in your first pull request, even for trivial fixes. The names are sorted lexicographically. To ensure your patch meets all the necessary requirements, please also see the Contributor Guidelines. Editors of the DOM Standard are expected to follow the Maintainer Guidelines. A dashboard showing the tests running against browser engines can be seen at wpt.fyi/results/dom. For quick local iteration, run make ; this will use a web service to build the standard, so that you don't have to install anything. See more in the Contributor Guidelines. Do not use newlines inside "inline" elements, even if that means exceeding the column width requirement. Using newlines between "inline" element tag names and their content is also forbidden. (This actually alters the content, by adding spaces.) That is Do not indent for anything except a new "block" element. For instance End tags may be included (if done consistently) and attributes may be quoted (using double quotes), though the prevalent theme is to omit end tags and not quote attributes (unless they contain a space). Place one newline between paragraphs (including list elements). Place three newlines before , and two newlines before other headings. This does not apply when a nested heading follows the parent heading. Use camel-case for variable names and "spaced" names for definitions, algorithms, etc.