Confirmed users
630
edits
MDN/Development/CompatibilityTables/Data Requirements: Difference between revisions
Jump to navigation
Jump to search
MDN/Development/CompatibilityTables/Data Requirements (view source)
Revision as of 15:43, 12 February 2014
, 12 February 2014→Compatibility markers
| Line 45: | Line 45: | ||
There are two ideas : | There are two ideas : | ||
# Allow to create in-line compatibility markers to provides quick information within our content. | |||
# Provide a very quick visual hint on top of the page to tell which browser currently support the features describe on the page (it can be a logo or anything else). | # Provide a very quick visual hint on top of the page to tell which browser currently support the features describe on the page (it can be a logo or anything else). | ||
The first idea is one of our functional priority as we already have such markers for Gecko/Firefox compatibility (but currently not bind to any formal compatibility data which requires some time consuming manual maintenance). | |||
The second idea is less important and require a deeper investigation as it can be tricky to provide an accurate information. Currently on MDN, most of our pages contain information about several features at the same time or information about feature which evolved greatly over time. Therefor, such information can be often misleading if not handled very carefully. More specificaly, Such summary information can hide inter-compatibility problems: the "support" may mean "it can be made work in this browser", "follow the spec, but maybe with a couple of minor glitch", "follow perfectly the spec". The flexbox support is one example: most modern browsers follow the spec, but maybe with a couple of minor glitch. But flexbox was available in one way or another in browsers long time ago (but interoperability was a nightmare to achieve). | |||
==== Compatibility Filters ==== | ==== Compatibility Filters ==== | ||