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 06:51, 13 July 2015
, 13 July 2015Added possible solution to 'unknown_kumascript'
(minor edits and fixes) |
Sebastianz (talk | contribs) (Added possible solution to 'unknown_kumascript') |
||
| Line 327: | Line 327: | ||
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. | 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. | ||
'' | ''Possible solutions'':<br /> | ||
* This is caused by a macro unknown to the importer, e.g. by using <code>geckoRelease</code> within the compatibility hints. If you feel, the importer should be able to handle the macro, file a bug against it, otherwise remove the macro. | |||