Another successful MDN doc sprint

While this weekend’s documentation sprint was smaller than the previous one, it represented significant steps toward achieving the goal of making Mozilla Developer Network a comprehensive, usable, and accurate resource for everyone developing for the web.

  • Eric Shepherd created and refined (and the rest of us began implementing) a format and related templates for browser compatibility tables for web technology reference pages. These tables will contain information about support for features in the major browsers, for both desktop and mobile platforms. Now the big task is to add the tables and browser support information to all of the many pages that need them.
  • In addition, Kang-Hao Lu created a template for indicating prefixed CSS properties, and used it in compatibility tables on several CSS property reference pages.
  • Collaboration with Google continued, with Kathy W updating the article on requestAnimationFrame with compatibility info for Chrome and Safari.
  • Jeremie Pationnier continued rocking the SVG reference, adding 17 new pages, improving several others, and adding the NeedsCompatTable tag to all of them.
  • Florian Scholz documented three more MathML elements, and added compatibility tables.
  • Trevor Hobson updated XUL elements and attributes to use templates for interface references.
  • David Bruant created compatibility tables and tested compatibility for JavaScript get and set operators.
  • Matheus Svolenski translated two more pages into Brazilian Portuguese.
  • Janet Swisher created a compatibility table for the HTML <input> element. The Firefox version information for the attributes and for values of the type attribute is now in this table rather than interspersed in the body of the page.

Thanks to everyone who participated!


  1. crash


    I’ve added data for Opera and Chrome for the input element? As I’ve done that, I’ve though about having the ability to add colors for supported (green), partial (orange), no support (red) and unknown (gray).

    And what should someone add when the attribute/element is supported for a long time?

    April 4th, 2011 at 01:03

  2. Janet Swisher

    You can use the CompatVersionUnknown template for cases where you know the browser supports the feature, but don’t know in what version the support started. Or you can something like “>=6.0”, when you know a version that supports it, but aren’t sure if that was the first one. The goal is to help web developers write code for their current users, so historical precision is not essential.

    April 15th, 2011 at 16:31

Comments are closed for this article.