Now we're getting somewhere!<div><br></div><div>I agree: Favicon support is *optional*. But if it is implemented, it is *required* to provide a user configuration setting, disabled by default, and if it is implemented, it is *strongly recommended* to provide the user the ability to upload a custom favicon.</div>
<div><br></div><div>Sound reasonable?</div><div><br></div><div>When we "finalize" our thoughts, I would propose this as a WordPress 3.1 Guideline change (along with making License/LicenseURI header tags *required*).</div>
<div><br></div><div>Chip<br><br><div class="gmail_quote">On Tue, Oct 19, 2010 at 3:29 PM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I think Otto's idea of a favicon is fine providing it can be readily changed without editing the theme files but via theme options.<br><br>... or in other words, the favicon should not be hard-coded into a theme although a theme is allowed to provide the functionality via its options panel(s).<br>
<br>We probably need some better wording on that, and maybe some sort of an idea how many existing themes it could be related to but we could likely go forward along those lines.<br><br><br>Cais.<div><div></div><div class="h5">
<br><br><div class="gmail_quote">
On Tue, Oct 19, 2010 at 4:19 PM, 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:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
I don't think there's anything inherently wrong with a theme-dependent<br>
favicon, in that people often want their favicon's to be similar to<br>
their themes. Matt had me change his to match when we changed up the<br>
theme for the new <a href="http://ma.tt" target="_blank">ma.tt</a>.<br>
<br>
I would say that if a theme provides the favicon code though, there<br>
should be a couple of rules<br>
1. The favicon should be using the *stylesheet_uri code, so that a<br>
child theme can easily override it like any other file in the theme<br>
(and ideally there should be some obvious way to disable this,<br>
preferably with it defaulting to disabled), or<br>
2. The theme should provide some easy way for a user to upload their<br>
own favicon (maybe in an advanced theme settings).<br>
<br>
If the theme is just splatting the favicon code out there, with no way<br>
to change it other than editing the theme, then that's bad. People<br>
don't want their favicon to be the same as other sites.<br>
<font color="#888888"><br>
-Otto<br>
</font><div><div></div><div>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">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></div><br>_______________________________________________<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>
<br></blockquote></div><br></div>