Re: The whole panel focus/keynav thing
- From: Luis Villa <louie ximian com>
- To: Bill Haneman <bill haneman sun com>
- Cc: "Padraig O'Briain" <Padraig Obriain sun com>, gnome-accessibility-list gnome org, desktop-devel-list gnome org, usability gnome org, calum benson sun com
- Subject: Re: The whole panel focus/keynav thing
- Date: 28 May 2002 16:45:26 -0400
On Tue, 2002-05-28 at 18:42, Bill Haneman wrote:
> On Tue, 2002-05-28 at 20:15, Luis Villa wrote:
> > On Tue, 2002-05-28 at 02:58, Padraig O'Briain wrote:
> > > I am not sure whether the patch went to the release team but it was discussed
> > > with Mark Mc Loughlin. Mark has now backed out the patch.
> > >
> > > So we we will have to come up with a new way of giving the user visual
> > > indication when focus is in a panel.
> >
> > So with the latest builds from this morning I (1) still have the broken
> > focus indication and (2) I now have a border around all applets on my
> > 'regular' panels, which (3) doesn't solve any focus indication problems
> > for hidden panels, (4) doesn't fix the menu bar, and (5) breaks
> > usability by making it impossible to click on the last several pixels of
> > the screen.
>
> #5 has been broken for GNOME2 panel forever I think. However there is a
> potential conflict between #5 and focus indication, if we fix #5.
Yeah, I was made aware of that after the email [and noted it in the
bug.]
> I don't think the border stuff is any of our doing, but am not 100%
> sure.
The current size of it is, I'm told? [Not the actual existence, no.]
Luis
> -Bill
>
> > I've documented all of these issues in bug 82887.
> > Luis
> >
> > > >
> > > > On Mon, 2002-05-27 at 16:30, Bill Haneman wrote:
> > > > > On Mon, 2002-05-27 at 20:33, Seth Nickell wrote:
> > > > > > On Mon, 2002-05-27 at 06:37, Bill Haneman wrote:
> > > > > > > Padraig/All:
> > > > > > >
> > > > > > > I don't think we should make such a statement without further
> > > > > > > researching the issues here.
> > > > > >
> > > > > > Yes we should. This close to release we should have backed the change
> > > > > > out a few days ago. It can be added back in if it can be made to work.
> > > > > > We shouldn't have regressions / new brokenness, period. Its not
> > > > > > difficult to add the changes in again if they can be made to work
> > > > > > smoothly. I don't see why that is not the automatic model we should be
> > > > > > following here ?!?
> > > > > >
> > > > > > That said, I would be much more comfortable if the changes would be run
> > > > > > by a release team member before they are committed since they *have* a
> > > > > > history of breaking things.
> > > > >
> > > > > The patch was posted for comments for over a week (maybe two) before
> > > > > being committed. RT members *were* consulted.
> > > >
> > > > Forgive me if I missed it, but searching through archives of the release
> > > > team list I don't see any mention of this patch.
> > > >
> > > > -Seth
> > > >
> > > > _______________________________________________
> > > > gnome-accessibility-list mailing list
> > > > gnome-accessibility-list gnome org
> > > > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
> > >
>
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]