Then I would propose the following:<div><br></div><div><ul><li>A general INFO comment on existence of wp_deregister_script()</li><li>If possible, a REQUIRED comment on existence of wp_deregister_script( $handle ), where $handle is <a href="http://codex.wordpress.org/Function_Reference/wp_enqueue_script#Default_scripts_included_with_WordPress">any of the core-bundled scripts</a>.</li>
</ul></div><div><br></div><div>I *think* that should cover our bases? Themes will auto-fail upon de-registering any core-bundled script, and reviewers will be flagged to verify any other usage of wp_deregister_script().</div>
<div><br></div><div>Chip<br><br><div class="gmail_quote">On Thu, May 31, 2012 at 7:40 AM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
There is the issue of child themes, obviously. Since we're allowing<br>
child themes as of 3.4, this may be a use case for them, so before<br>
adding it to theme check, it needs to be more well-defined as to what<br>
the "check" is doing and such.<br>
<br>
Child themes de-registering scripts in the parent in order to replace<br>
the script is valid.<br>
<span class="HOEnZb"><font color="#888888"><br>
-Otto<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</div></div></blockquote></div><br></div>