1208914 - [CompatData] Treat "Basic Support" rows as referring to page feature

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: General, enhancement)

Description

[John Whitlock [:jwhitlock]]

What problem would this feature solve?
======================================
Many pages include a "Basic Support" row, often as the only row, but in many cases to cover the most common usage of a feature.  This is currently imported as a row feature with a localizable name, leaving the page feature without support data.

Instead, treat the "Basic Support" row as defining support for the page feature.  "Basic Support" would then be consistently localized in the client.

Who has this problem?
=====================
Staff contributors to MDN

How do you know that the users identified above have this problem?
==================================================================
"Basic Support" is used on hundreds, if not thousands, of pages, and represents an unnecessary localization burden.

How are the users identified above solving this problem now?
============================================================
Translators localize the phrase into their own language

Do you have any suggestions for solving the problem? Please explain in detail.
==============================================================================
The importer would treat items in the "Basic Support" row as referring to the page feature.  BrowserCompat sample displays would add a 'Basic Support' row if the page feature has support information.  {{EmbedCompatDisplay}} would do the same.  Existing "Basic Support" rows would be manually deleted.

Is there anything else we should know?
======================================

Comment 1

[MDN Team (:mdn-dev)]

Commits pushed to master at https://github.com/mdn/browsercompat

https://github.com/mdn/browsercompat/commit/eae9b92eb36e7bfe9800bbffc2e850cdec50f918
bug 1208914 - Use different feature row test case

The "Basic Support" row will describe the page feature, not be converted
to a child row. Use "contain and cover" as the feature row test case.
Because it has a different letter count, issue offsets also changed.

https://github.com/mdn/browsercompat/commit/7094087561e5ad5f676ae08ba7d20a0d9e3477bf
bug 1208914 - Apply Basic Support to feature

Instead of importing "Basic Suport" rows as a new child feature, apply
this row of support details to the subject feature page.

https://github.com/mdn/browsercompat/commit/428d5b69c282d804c59a7e14cdf95f784dfc8472
fix bug 1208914 - Update display for Basic Support

Update the JS and Jinja2 displays of sample data to add a row "Basic
Support" when there is support information for the target feature.  Add
some translations of "Basic Support".  This might be the start of
localization of other strings, such as "Desktop Browsers" and "Feature".