On 12/11/2015 12:28 AM, Alexander Surkov wrote:
I guess it isn't an edge case after all. I was originally confused by
using child indexes in the case of no text, as this seems strange to me.
I'm not sure where we are on this idea. Do you think we'd rather drop it?
Personally, I'd rather have a separate mechanism to deal with selected
objects in a container. I think it's just going to get too confusing
otherwise.
I don't really follow this. As I understand it, selection starts
are inclusive and selection ends are exclusive. So, why are we
talking about "before" a child? If you have 4 children and
children 2 and 3 are selected, IMO, the start offset should be 1
(the selection starts at the second child) and the end offset
should be 3 (the selection ends after the third child). Maybe this
is just terminology; it doesn't really matter so long as we agree
on the numbers. :)
I'm not sure I have clear understanding how values differs for
inclusive and exclusive end boundaries. Can you give me please an
example for, say, when a container has one child and it is selected,
i.e selection starts before it and ends after it?
The way I think of text (and maybe this is wrong visually), if you have
the string "a" and you select it, the selection starts *at* the "a" and
ends *after* it. So, in that case, start would be 0 and end would be 1.
Similarly, if you have just one child, start would be 0 and end would be
1. I have a feeling we're actually talking about the same thing, but you
see the seleciton as starting "before", not "at".
Jamie
--
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: [email protected]
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
