Closed
Bug 1063570
Opened 11 years ago
Closed 10 years ago
[Compat Data] Convert feature.maturity to flags
Categories
(developer.mozilla.org Graveyard :: General, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jwhitlock, Unassigned)
References
Details
(Whiteboard: [specification][type:feature])
What problems would this solve?
===============================
According to experts, feature maturity can't be expressed as one of several states. Instead, convert to several flags.
Who would use this?
===================
Developers who are concerned about the maturity of a feature before using it.
What would users see?
=====================
API users would see a detailed explanation of the feature maturity. MDN users would see a quick visual indication such as a beaker icon, with additional details in a hover or popup.
What would users do? What would happen as a result?
===================================================
Developers and designers would quickly be able to tell what features are experimental, and plan accordingly.
Is there anything else we should know?
======================================
Based on a discussion at this mailing list:
https://groups.google.com/forum/#!topic/mozilla.dev.mdn/hKh9Ib7nQgY
Github issue: https://github.com/jwhitlock/web-platform-compat/issues/8
Reporter | ||
Comment 1•11 years ago
|
||
Jean-Yves Perrier proposed these flags:
feature.experimental - The spec is not ratified, such as CSS Transitions, ES6, and DOM Living Standard
feature.standard - The feature is described in a standards-track spec
feature.stable - The feature is considered stable
Stephanie Hobson proposed:
feature.obsolete
Reporter | ||
Comment 2•11 years ago
|
||
Docs updated in https://github.com/mozilla/web-platform-compat/commit/473458e
Merged with PR #1: https://github.com/mozilla/web-platform-compat/pull/1
Docs live at: http://web-platform-compat.readthedocs.org/en/latest/draft/resources.html#features
Implementation still to do.
Reporter | ||
Comment 3•10 years ago
|
||
This should be closed, it was implemented quite a while ago:
https://browsercompat.herokuapp.com/api/v1/features/1136
Flags: needinfo?(lcrouch)
Comment 4•10 years ago
|
||
Resolving fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(lcrouch)
Resolution: --- → FIXED
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•