MDN/Archives/Development/CompatibilityTables/Importer: Difference between revisions

inline_text: demonstrate changing prose description of changing support to importable version
(Added second solution to 'halt_import' error)
(inline_text: demonstrate changing prose description of changing support to importable version)
Line 257: Line 257:


* A common case that causes this error is where you insert a browser version number or compatibility macro into a Browser compatibility table, but then want to include some supporting data or information about an edge case or quirk next to or just below it. The correct way to deal with this is to insert the extra information as a footnote — see the [https://developer.mozilla.org/en-US/docs/Web/API/Element/querySelector#Browser_compatibility Element.querySelector Browser compat table] for an example of correct usage.
* A common case that causes this error is where you insert a browser version number or compatibility macro into a Browser compatibility table, but then want to include some supporting data or information about an edge case or quirk next to or just below it. The correct way to deal with this is to insert the extra information as a footnote — see the [https://developer.mozilla.org/en-US/docs/Web/API/Element/querySelector#Browser_compatibility Element.querySelector Browser compat table] for an example of correct usage.
* Prose descriptions of changing support should be modified to use the compatibility KumaScript macros.  For example, [https://developer.mozilla.org/en-US/docs/Web/API/Coordinates Web/API/Coordinates] included the saga of changing support in Opera:
<pre>
<td>
    10.60 <br>
    Removed in 15.0 <br>
    Reintroduced in 16.0
</td>
</pre>
This changes to:
<pre>
<td>
    10.60 <br>
    {{CompatNo}} 15.0 <br>
    16.0
</td>
</pre>


=== nested_p ===
=== nested_p ===
67

edits