<div class="gmail_quote">On Tue, Oct 19, 2010 at 3:13 PM, Simon Prosser <span dir="ltr"><<a href="mailto:pross@pross.org.uk">pross@pross.org.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 10/19/10 21:11, Chip Bennett wrote:<br>
> Yes, and a /Plugin/ is the correct way for the user to change the<br>
> Favicon - so that it isn't /Theme-dependent/.<br>
><br>
> If a user installs a Plugin to manage the site's Favicon, then the user<br>
</div>> would expect the /Plugin/ to be managing the Favicon, not the /Theme/.<br>
Right!<br>
<br>
This is yet another candidate for a theme install/uninstall hook to set<br>
a blank favicon on uninstall or theme switch would make Chip a happy chappy.</blockquote><div><br></div><div>Very much so - and for more than just Favicons. :)</div><div><br></div><div>But it's still a secondary issue to a Theme changing identity/branding content without user permission.</div>
<div><br></div><div>Chip</div></div>