- From: Janet Swisher <jswisher@mozilla.com>
- Date: Thu, 24 Jan 2013 20:36:42 -0600
- To: public-webplatform@w3.org
- Message-ID: <5101EFBA.9060904@mozilla.com>
On 1/23/13 9:01 PM, Alex Komoroske wrote: > We need to carefully think about the compatibility table design; this > is a complex area and we shouldn't jump into a given design without > considering the consequences. Font-size is a pretty straightforward > property, but other complications to consider include: how to show > that support started prefixed at one version and unprefixed at > another, as well as how to include information about sub-compatiblity > information. For example, MDN's box-shadow page [1] has four separate > rows for basic support, multiples, inset, and spread radius. That > said, I like this compatibility design a fair bit; the use of color > for supported status makes it work both at a glance and when you want > specific versions. > > Thanks for doing such an awesome job on this! > > --Alex > > [1] https://developer.mozilla.org/en-US/docs/CSS/box-shadow > The HTML <input> element is my standard example of a worst-case scenario for compatibility tables: https://developer.mozilla.org/en-US/docs/HTML/element/input#Browser_compatibility -- Janet Swisher <mailto:jREMOVEswisher@mozilla.com> Mozilla Developer Network <https://developer.mozilla.org> Technical Writer/Community Steward
Received on Friday, 25 January 2013 02:37:11 UTC