[Compat Data] Use support.support=no when a non-default config is needed

RESOLVED FIXED

Status

Mozilla Developer Network
General
--
enhancement
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: jwhitlock, Unassigned)

Tracking

Details

(Whiteboard: [specification][type:feature])

(Reporter)

Description

3 years ago
What problems would this solve?
===============================
Part of the standardization process is building implementations of new features.  In 2015, these are often included in new clients, but require configuration to enable.  When enabled, these may fully support the proposed feature, but saying support=yes or support=partial is misleading to developers

Who would use this?
===================
Developers looking for compatibility information.  Contributors adding compatibility information.

What would users see?
=====================
Developers would see support=No for features that require a non-default configuration to enable.  Contributors would only be allowed to select support=No.

What would users do? What would happen as a result?
===================================================
Developers will read the notes and learn more about the feature.

Is there anything else we should know?
======================================
The discussion started on January 21st, 2015 on the mdn-drivers list [1].  The decision was made on January 30th, 2015 [2].

It was also decided that, when importing prefixed features from MDN, support=Yes if there is no note, and support=Partial if there is a note.  Contributors can adjust the support after import if they have expertise in that feature and implementation.

[1] https://groups.google.com/forum/#!topic/mozilla.mdn.drivers/T32k4vy-eNs
[2] https://groups.google.com/forum/#!topic/mozilla.mdn.drivers/tzNR96C_EsM
(Reporter)

Updated

3 years ago
Blocks: 996570
Severity: normal → enhancement

Comment 1

3 years ago
Commit pushed to master at https://github.com/mozilla/web-platform-compat

https://github.com/mozilla/web-platform-compat/commit/80c77d706a836c33ea2e0df3e99e3a350806f418
bug 1128531 - prefix + footnote => partial support

If a support has both a prefix and a footnote, assume that the feature
is in flux and support is partial.
(Reporter)

Comment 2

3 years ago
Should have used "fix bug 1128531".  groovecoder, can you close this bug?
Flags: needinfo?(lcrouch)
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Flags: needinfo?(lcrouch)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.