On Tue, Dec 8, 2009 at 4:59 PM, Evan Stade <est...@chromium.org> wrote:
>
> this makes the assumption that there is some "best" setting for each WM,
> which is false. What's best for me on metacity is not what's best for you on
> metacity.
>
Unfortunately, if you really believe that, then for one of us the default is
wrong, and statistically the aggrieved party is unlikely to find,
understand, and change the option. The option doesn't actually solve the
problem the majority of the time.
Therefore, in most cases we should just pick what we think is best, and let
people who don't like it either adapt or leave, because that reduces
cognitive friction, support costs, and code complexity. Unfortunately in
this case we're talking about supporting both codepaths, which nixes the
maintenance pluses. We still get fewer user choices though, which would be
enough for me.
there have been many, many, many bugs where a user requests some random
> functionality provided by their particular WM, and our only answer (save
> re-implementing the functionality) is to tell them to disable the custom
> frame.
>
This is why I said the default should be "window manager frame for all WMs
we have not explicitly whitelisted". We can only get away with the custom
frame if we know it will work well.
PK
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
