1188096 - Convert Web/API/Element/Input to new compat table on staging

Status: RESOLVED WONTFIX

(developer.mozilla.org Graveyard :: BrowserCompat, defect)

Description

[John Whitlock [:jwhitlock]]

What problem would this feature solve?
======================================
The page is using the current compatibility table, not the new one.  Converting this page may highlight issues in the new tables or the API.

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

How do you know that the users identified above have this problem?
==================================================================
It takes too many manual steps to get this page onto the new table in a development environment, and has been done by no one.

How are the users identified above solving this problem now?
============================================================
They are not solving it.

Do you have any suggestions for solving the problem? Please explain in detail.
==============================================================================
Convert this page to use the new compatibility code:

- Web/API/Element
  * Complex example, on shobson's list
  * Slug web-api-element
  * https://developer.mozilla.org/en-US/docs/Web/API/Element#Browser_compatibility
  * https://developer.allizom.org/en-US/docs/Web/API/Element#Browser_compatibility
  * https://browsercompat.herokuapp.com/importer/91
  * https://browsercompat.herokuapp.com/api/v1/view_features/web-html-element-input (skeleton, paginated)

Is there anything else we should know?
======================================
It is currently not importing due to parser issues on the specification description.  It also has a similar complication to Web/JavaScript/Reference/Global_Objects/Array, including sub-MDN pages as child pages.

Comment 1

[John Whitlock [:jwhitlock]]

The BrowserCompat project is canceled.  See https://github.com/mdn/browsercompat for current effort. Bulk status change includes the random word TEMPOTHRONE.