Note: If you came to this page from a link on https://browsercompat.herokuapp.com/importer, then it may be that additional documentation has not been written for the importer issue. Feel free to add a Level 3 heading for your issue.
General Information
It is not enough to create a data store for compatibility data. It also needs to be populated with structured data. We've decided to start with MDN data, rather than start from scratch or an existing data source. An MDN data importer is now part of the web-platform-compat project, and is live at https://browsercompat.herokuapp.com/importer/.
The Issues
The importer identifies classes of issues with a slug, a short span of text. The sections below use those slugs as the title, so that we can link directly from the importer to advice for handling that class of issue.
bad_json
Error template:
Response from {url} is not JSON
Actual content:
{content}
No one has contributed hints for handling this issue yet.
compatgeckodesktop_unknown
Error template:
Unknown Gecko version "{version}"
The importer does not recognize this version for CompatGeckoDesktop. Change the MDN page or update the importer.
No one has contributed hints for handling this issue yet.
compatgeckofxos_override
Error template:
Override "{override}" is invalid for Gecko version "{version}".
The importer does not recognize this override for CompatGeckoFxOS. Change the MDN page or update the importer.
No one has contributed hints for handling this issue yet.
compatgeckofxos_unknown
Error template:
Unknown Gecko version "{version}"
The importer does not recognize this version for CompatGeckoFxOS. Change the MDN page or update the importer.
No one has contributed hints for handling this issue yet.
exception
Error template:
Unhandled exception
{traceback}
No one has contributed hints for handling this issue yet.
extra_cell
Error template:
Extra cell in compatibility table row.
A row in the compatibility table has more cells than the header row. It may be the cell identified in the context, a different cell in the row, or a missing header cell.
No one has contributed hints for handling this issue yet.
failed_download
Error template:
Failed to download {url}.
Status {status}, Content:
{text}
No one has contributed hints for handling this issue yet.
false_start
Error template:
No <h2> found in page.
A compatibility table must be after a proper <h2> to be imported.
No one has contributed hints for handling this issue yet.
footnote_feature
Error template:
Footnotes are not allowed on features
The Feature model does not include a notes field. Remove the footnote from the feature.
No one has contributed hints for handling this issue yet.
footnote_missing
Error template:
Footnote [{footnote_id}] not found.
The compatibility table has a reference to footnote "{footnote_id}", but no matching footnote was found. This may be due to parse issues in the footnotes section, a typo in the MDN page, or a footnote that was removed without removing the footnote reference from the table.
No one has contributed hints for handling this issue yet.
footnote_multiple
Error template:
Only one footnote allowed per compatibility cell.
The API supports only one footnote per support assertion. Combine footnotes [{prev_footnote_id}] and [{footnote_id}], or remove one of them.
No one has contributed hints for handling this issue yet.
footnote_no_id
Error template:
Footnote has no ID.
Footnote references, such as [1], are used to link the footnote to the support assertion in the compatibility table. Reformat the MDN page to use footnote references.
No one has contributed hints for handling this issue yet.
footnote_unused
Error template:
Footnote [{footnote_id}] is unused.
No cells in the compatibility table included the footnote reference [{footnote_id}]. This could be due to a issue importing the compatibility cell, a typo on the MDN page, or an extra footnote that should be removed from the MDN page.
No one has contributed hints for handling this issue yet.
halt_import
Error template:
Unable to finish importing MDN page.
The importer was unable to finish parsing the MDN page. This may be due to a duplicated section, or other unexpected content.
No one has contributed hints for handling this issue yet.
inline_text
Error template:
Unknown inline support text "{text}".
The API schema does not include inline notes. This text needs to be converted to a footnote, converted to a support attribute (which may require an importer update), or removed.
No one has contributed hints for handling this issue yet.
nested_p
Error template:
Nested <p> tags are not supported.
Edit the MDN page to remove the nested <p> tag
No one has contributed hints for handling this issue yet.
section_missed
Error template:
Section <h2>{title}</h2> was not imported.
The import of section {title} failed, but no parse error was detected. This is usually because of a previous critical error, which must be cleared before any parsing can be attempted.
No one has contributed hints for handling this issue yet.
section_skipped
Error template:
Section <h2>{title}</h2> has unexpected content.
The parser was trying to match rule "{rule_name}", but was unable to understand some unexpected content. This may be markup or text, or a side-effect of previous issues. Look closely at the context (as well as any previous issues) to find the problem content.
No one has contributed hints for handling this issue yet.
spec_h2_id
Error template:
Expected <h2 id="Specifications">, actual id=Template:H2 id
Fix the id so that the table of contents, other feature work.
No one has contributed hints for handling this issue yet.
spec_h2_name
Error template:
Expected <h2 name="Specifications">, actual name=Template:H2 name
Fix or remove the name attribute.
No one has contributed hints for handling this issue yet.
spec_mismatch
Error template:
SpecName({specname_key}, ...) does not match Spec2({spec2_key}).
SpecName and Spec2 must refer to the same mdn_key. Update the MDN page.
No one has contributed hints for handling this issue yet.
unknown_browser
Error template:
Unknown Browser "{name}".
The API does not have a browser with the name "{name}". This could be a typo on the MDN page, or the browser needs to be added to the API.
No one has contributed hints for handling this issue yet.
unknown_kumascript
Error template:
Unknown KumaScript {display} in {scope}.
The importer has to run custom code to import KumaScript, and it hasn't been taught how to import {name} when it appears in a {scope}. File a bug, or convert the MDN page to not use this KumaScript macro.
No one has contributed hints for handling this issue yet.
unknown_spec
Error template:
Unknown Specification "{key}".
The API does not have a specification with mdn_key "{key}". This could be a typo on the MDN page, or the specfication needs to be added to the API.
No one has contributed hints for handling this issue yet.
unknown_version
Error template:
Unknown version "{version}" for browser "{browser_name}"
The API does not have a version "{version}" for browser "{browser_name} (id {browser_id}, slug "{browser_slug}"). This could be a typo on the MDN page, or the version needs to be added to the API.
No one has contributed hints for handling this issue yet.