MDN/Development/CompatibilityTables/Data Requirements: Difference between revisions

Jump to navigation Jump to search
Line 57: Line 57:


To provide useful information we need to clearly define the features we are providing information about.
To provide useful information we need to clearly define the features we are providing information about.
'''QUESTION:''' ''We need to handle sub-features such as specific values for CSS properties (see [https://developer.mozilla.org/en-US/docs/Web/CSS/display display]) or different Function signature or return value for JavaScript function (see [https://developer.mozilla.org/en-US/docs/Web/API/MozMobileMessageManager.getSegmentInfoForText getSegmentInfoForText]). How to do this?''


==== Name ====
==== Name ====
Line 74: Line 72:
'''QUESTION:''' ''Do we need that name to be localisable?''
'''QUESTION:''' ''Do we need that name to be localisable?''


=== Feature sets ===
There are many cases where we want to display different level of detail regarding support for features. So it is somewhat helpful to organize feature into feature sets.
'''EXAMPLES:''' ''Each various values of a given CSS property are considered individuals features where the property as a whole is considered a feature set (see [https://developer.mozilla.org/en-US/docs/Web/CSS/display display]). Each attribute and methods are considered individuals features of a given API, which is a feature set. Even a methods can be a feature set if it has different signature, and each of them is an individual feature (see [https://developer.mozilla.org/en-US/docs/Web/API/MozMobileMessageManager.getSegmentInfoForText getSegmentInfoForText]).''


=== Specification ===
=== Specification ===
Confirmed users
630

edits

Navigation menu