Pointer grabs causing accessibility issues! Why not deprecate them?

[Xavier Bestel]

On Wed, 2008-04-30 at 23:29 +0930, Peter Hutterer wrote:
> Daniel Stone wrote:
> > On Wed, Apr 30, 2008 at 09:35:45AM -0400, Joel Feiner wrote:
> >> I had wondered this myself.  In Windows, if you have a popup/dropdown 
> >> menu open, when you mouseover other elements on the screen, they still 
> >> highlight, even if they don't belong to the current application.  With 
> >> X, only the current application will still highlight.  Also, if you 
> >> click on something outside the dropdown menu, it is immediately 
> >> activated and the menu is closed.  On X, you have to click twice: once 
> >> to close the menu and again to activate whatever widget your mouse is 
> >> now over.
> >>
> >> The question is: what does Windows do here different from X?  Somehow 
> >> the application in question is notified that there is a click outside 
> >> the menu (thus closing it), but other apps still receive events just 
> >> fine.  Why can't X do something like this?
> > 
> > Hi,
> > There's nothing stopping X from doing this; it's just that it doesn't,
> > and doing so would be a pretty serious protocol/ABI/API break.  
> 
> you could do it now, but you'd have to request synchronised grabs for 
> popup menu, a full roundtrip for each event. This is not feasable.

Windows applications running under wine (under X) behave a bit like
that: you can have a menu open, and then click on another button and
it'll be activated. But that works only in the same app.

	Xav