Confirm
630
edits
Changes
→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]).''
The level of details to display can change with the display context. For example, if a feature set has one feature that is fully implemented, a feature that is partially implemented and a feature that is not implemented, what is the level of support for that feature set? There are three way of dispatching the same information:
1. If we want a optimistic view, the answer to the question "Does the feature set is implemented?" will be "Yes".
2. If we want a realistic view, the answer to the question "Does the feature set is implemented?" will be "Partially".
3. If we want a pessimistic view, the answer to the question "Does the feature set is implemented?" will be "No".
The three answers are acceptable, depending on the context so we need to be able to display each of the answers.
The same occurs when it come to know if a group of feature sets is supported or not by one or more browsers.
=== Specification ===
