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

MDN/Archives/Development/CompatibilityTables/Importer (view source)

25 bytes added , 23 January 2016

Updated possible solutions for 'unknown_kumascript' error

Confirmed users

233

edits

@@ Line 423: / Line 423: @@
 ''Possible solutions'':<br />
-* This is caused by a macro unknown to the importer, e.g. by using <code>geckoRelease</code> within the compatibility hints. This is already filed as [https://bugzilla.mozilla.org/show_bug.cgi?id=1134450 bug 1134450]. 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.
+* This is caused by a macro unknown to the importer. This can happen within the compatibility hints or the cells of the compatibility table. E.g. this error happens when there is an <code>unimplemented_inline</code> or an <code>unimplemented_inline_webkit</code> macro 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.
-* The error can also happen within a compatibility cell, e.g. by a the <code>Bug</code> macro next to the version number. In those cases create a new compatibility note for that version and move the macro there.
+* 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.