<div dir="ltr">Setting $content_width inside of a callback allows it to be overridden by a Child Theme. Putting it in the global scope makes it impossible to override.</div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Mon, Jan 21, 2013 at 9:01 AM, Michael Fields <span dir="ltr"><<a href="mailto:michael@mfields.org" target="_blank">michael@mfields.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In regards to $content_width. This is a global variable recognized by core. Conditionally setting it in the global scope is perfectly OK. Themes that do this work just as well as themes that hook it into after_setup_theme. I do not understand why setting it in the global scope would be a requirement. All of the bundled "Twenty" themes do it this way.<br>
<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>