Re: Ignored windows are not 100% ignored?
Re: Ignored windows are not 100% ignored?
- Subject: Re: Ignored windows are not 100% ignored?
- From: Håkan Waara <email@hidden>
- Date: Wed, 7 Jun 2006 21:46:53 +0200
7 jun 2006 kl. 18.51 skrev Mike Engber:
Ignored ui elements are intended to be used for eliminating
intermediate views (e.g. clip views) that aren't a visible part of
the ui. Sometimes people get away with using accessibilityIsIgnored
to hide part of the hierarchy, but as you've discovered, this
doesn't work when there are children involved.
Hiding part of the hierarchy requires ensuring nothing returns
anything in that hierarchy - e.g. as children, from hit testing,
focus testing, any other attributes whose value is a ui element, ...
Ah right, so if I return an empty array for the AXChildren attr, it
will work right?
Is the window you're trying to hide visible to the user? If it is,
it doesn't seem proper for you to hide it from accessibility.
This was merely a quick test if I could hide a whole visible window
(and its children) from the hierarchy. I hadn't gotten to the step of
implementing the proper return values for attributes yet.
I won't actually want to block visible windows later, only hidden ones.
/Håkan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden