[wp-hackers] WP 3.1 admin bar

[Chip Bennett]

I don't believe that *most* users would do any such thing.

I believe that *most* users, when they learn about a new feature due to that
new feature changing something about the appearance or output of their site,
are going to be quite unhappy that said new feature was enabled - and thus,
changed their site - without permission.

New features that change the public-facing appearance or output of users'
sites should not be enabled by default.

But, again: this argument was had months ago, and those who espouse my
opinion lost that argument. There's really not much sense in re-hashing it
now.

Chip

On Thu, Feb 17, 2011 at 1:46 PM, Iain Cambridge <backie at backie.org> wrote:

> If it happened like that most people would either never find out about new
> features, complain it wasn't enabled by default or claim their is a bug
> because it wasn't enabled.
>
> Iain
>
> On 17 February 2011 19:22, Blue Chives <info at bluechives.com> wrote:
>
> > Like it but it won't happen.
> >
> >
> > On 17 Feb 2011, at 18:56, Mark E wrote:
> >
> > > +1 on that.
> > >
> > > On 02/17/2011 11:27 AM, Chris Williams wrote:
> > >> I like that approach.
> > >>
> > >> On 2/17/11 9:39 AM, "Chip Bennett"<chip at chipbennett.net>  wrote:
> > >>
> > >>> I think there is merit, though, in the suggestion that the feature be
> > >>> turned
> > >>> ON by default for NEW installations, and turned OFF by default for
> > >>> upgrades.
> > > _______________________________________________
> > > wp-hackers mailing list
> > > wp-hackers at lists.automattic.com
> > > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>