Add browser version to compat table even when the support is behind a pref?

[Sebastian Zartner]

Currently we mention the browser version of a feature within the compatibility table even when the feature is behind a preference (defaulting to false). In that case a footnote clarifies that you to enable the preference first before you're able to use it. See for example the CSS grid properties[1] or the -webkit prefixed features.

Daniel Holbert noted in bug 1176968[2] that this might be confusing for readers, because it looks like the browser claims to support the feature but it is actually not available by default.

Unfortunately our contributor documentation[3] does not mention what to do in this case.

So, should we keep mentioning the version that introduced the experimental implementation the feature or should we add {{CompatNo}} instead (and keep the clarifying footnote) until the preference defaults to true?

Sebastian

[1] https://developer.mozilla.org/en-US/docs/tag/CSS%20Grid
[2] https://bugzil.la/1176968#c20
[3] https://developer.mozilla.org/en-US/docs/MDN/Contribute/Structures/Compatibility_tables

[Stephanie Hobson]

Based on my research for the Brower Compat project the convention, and the
agreement on the mailing list was: if it's behind a pref the browser does
not support it.

So, sounds like CompatNo with the footnote.

Stephanie.

> _______________________________________________
> dev-mdc mailing list
> dev...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-mdc
> MDN contributor guide: http://bit.ly/ContributorGuide
>

[Janet Swisher]

I agree. Compatibility tables should be about what users experience "in
the wild", and not about what developers and power users can experience
if they flip a preference.

However, if we're currently doing it one way, and switch to doing it the
opposite way, we are likely to have a lot of data in an inconsistent
state for a long while.

--

Janet Swisher <mailto:jREMOVE...@mozilla.com>
Mozilla Developer Network <https://developer.mozilla.org>
Community Strategist

[Sebastian Zartner]

Thank you, Janet and Stephanie, for your feedback!

I've extended the contributor description[1] now to add {{CompatNo}}
when the feature is behind a pref.
And yes, we'll be in an inconsistent state for some time, though
because there was no clear rule so far, we are already in that state
now.

Sebastian

[1] https://developer.mozilla.org/en-US/docs/MDN/Contribute/Structures/Compatibility_tables#Templates_to_use_in_the_compatibility_table

> Mozilla Developer Network
> Community Strategist