Confirmed users
233
edits
MDN/Archives/Development/CompatibilityTables/Importer: Difference between revisions
Jump to navigation
Jump to search
MDN/Archives/Development/CompatibilityTables/Importer (view source)
Revision as of 11:05, 3 August 2015
, 3 August 2015Added description about 'WhyNoSpecStart' and 'WhyNoSpecEnd' macros
Sebastianz (talk | contribs) (Improved formatting of 'section_skipped' section) |
Sebastianz (talk | contribs) (Added description about 'WhyNoSpecStart' and 'WhyNoSpecEnd' macros) |
||
| Line 323: | Line 323: | ||
''Possible solutions'':<br /> | ''Possible solutions'':<br /> | ||
* Often, this is caused by the use of plain text or HTML instead of an expected KumaScript macro. For instance, [https://developer.mozilla.org/en-US/docs/MDN/Contribute/Content/Specification_tables specification tables] should be using the <code>SpecName</code> and <code>Spec2</code> macros instead of specifying text directly. | * Often, this is caused by the use of plain text or HTML instead of an expected KumaScript macro. For instance, [https://developer.mozilla.org/en-US/docs/MDN/Contribute/Content/Specification_tables specification tables] should be using the <code>SpecName</code> and <code>Spec2</code> macros instead of specifying text directly. If there is no specification for the described feature, you need to wrap the text into <code>WhyNoSpecStart</code> and <code>WhyNoSpecEnd</code> macros. | ||
* When the proper [https://developer.mozilla.org/en-US/docs/MDN/Contribute/Content/Specification_tables specification tables] and macros are not used, and instead a simple link to the spec is provided, follow these steps to resolve (the example I fixed when writing these steps was [https://developer.mozilla.org/en-US/docs/Web/API/TimeRanges/start Timeranges.start()]): | * When the proper [https://developer.mozilla.org/en-US/docs/MDN/Contribute/Content/Specification_tables specification tables] and macros are not used, and instead a simple link to the spec is provided, follow these steps to resolve (the example I fixed when writing these steps was [https://developer.mozilla.org/en-US/docs/Web/API/TimeRanges/start Timeranges.start()]): | ||