+1 to this:<div><br></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><span class="Apple-style-span" style="color: rgb(51, 51, 51); font-family: arial, sans-serif; font-size: 13px; background-color: rgb(255, 255, 255); "><b>With that said, WP's handling of this is crap.</b></span></div>
</blockquote><div><br></div><div>And therein lies the problem with even considering making it a requirement. The underlying implementation (inline styles by default, and force Theme developers to remove them via filter) impedes Theme developers - but I've tried to fight that fight, and lost. So, as long as WordPress core continues NOT to do it right, I think it would be an unreasonable burden on Theme developers to *require* them to support more than the default number of columns.</div>
<div><br></div><div>Chip<br><br><div class="gmail_quote">On Sat, Jul 16, 2011 at 6:33 PM, Justin Tadlock <span dir="ltr"><<a href="mailto:justin@justintadlock.com">justin@justintadlock.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Part of me thinks it should be a requirement. WordPress already handles styles for 1 - 10 columns (and more) by default. If a theme is overwriting this with custom styles or removing the inline <style> WP adds, they need to handle this on their own. That's where the biggest problem is -- themes overwriting this but not handling anything other than 3 columns.<br>
<br>
With that said, WP's handling of this is crap. I've never designed a theme where it doesn't break with the default WP styles. Of course, I always roll my own handling of this anyway.<div><div></div><div class="h5">
<br>
<br>
On 7/15/2011 5:39 PM, Ian Stewart wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 2011-07-15, at 5:36 PM, Chip Bennett wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Personally, I wasn't even thinking along those lines. Making something like that a *requirement* seems, IMHO, to cross the line into dictating design intent.<br>
<br>
The idea of adding it as a *recommendation* would merely be to raise awareness of an area that Theme developers may not previously have considered styling.<br>
</blockquote>
Sounds good to me.<br>
<br>
Ian Stewart<br>
<br>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
<br>
<br>
</blockquote>
______________________________<u></u>_________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.<u></u>wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/<u></u>mailman/listinfo/theme-<u></u>reviewers</a><br>
</div></div></blockquote></div><br></div>