Confirmed users
630
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 15:20, 1 February 2016
, 1 February 2016→unknown_kumascript
Sebastianz (talk | contribs) (Updated possible solutions for 'unknown_kumascript' error) |
|||
| Line 423: | Line 423: | ||
''Possible solutions'':<br /> | ''Possible solutions'':<br /> | ||
* This is caused by a macro unknown to the importer. This can happen within the compatibility hints or the cells of the compatibility table. | * This is caused by a macro unknown to the importer. This can happen within the compatibility hints or the cells of the compatibility table. Current known issues: | ||
** <code>unimplemented_inline</code> or an <code>unimplemented_inline_webkit</code> macro is put next to the version number within a compatibility cell. This macro should be moved to a footnote and replaced by a <code>bug</code> macro or <code>webkitbug</code> macro respectively. | |||
** <code>SVGRef</code> is put at the bottom of the page and is considered as part of the footnotes. This macro should be moved at the top of the page. | |||
* If you feel, your issue is not covered by that bug and the importer should be able to handle the macro, file a new bug against it and mark it as blocker for [https://bugzilla.mozilla.org/show_bug.cgi?id=1132269 bug 1132269], otherwise remove the macro. | * If you feel, your issue is not covered by that bug and the importer should be able to handle the macro, file a new bug against it and mark it as blocker for [https://bugzilla.mozilla.org/show_bug.cgi?id=1132269 bug 1132269], otherwise remove the macro. | ||
=== unknown_spec === | === unknown_spec === | ||