James Teh
> cc
>
> IAccessible2 mailing list ,
> Rob Gallo
> Subject
>
> Re: [Accessibility-ia2] Fwd: text attribute range calculation
> Hi, guys. One more question.
>
> Should we expose any text attributes for a range containing embedded
> characters? I lean tow
On 19/05/2010 10:38 PM, Alexander Surkov wrote:
> Should we expose any text attributes for a range containing embedded
> characters?
I'll assume you mean a range containing *only* embedded object characters.
> I lean towards to think we should return empty string for
> text attributes since text a
05/19/2010 07:38 Subject
AMRe: [Accessibility-ia2] Fwd: text
attribute range calculation
Hi, guys. One more question.
Should we expose any text attributes for a range containing embedded
characters? I lean towards to think we should return empty string for
text attributes since text attributes makes sense for normal text
only.
Thank you.
Alex.
On Wed, May 19, 2010 at 3:03 PM, Alexan
Ok, thanks James. I'll come with Rob's approach, then I will send try
Firefox build to Orca developers to check if performance is good
enough.
Alex.
On Wed, May 19, 2010 at 1:09 PM, James Teh wrote:
> On 18/05/2010 11:52 PM, Alexander Surkov wrote:
>> Aaron suggestion was like [*plain*plain**)[
On 18/05/2010 11:52 PM, Alexander Surkov wrote:
> Aaron suggestion was like [*plain*plain**)[bold*bold*), which I come here
> with.
This is the most complicated and potentially confusing, but also the
least expensive for out-of-process clients. Have you had any feedback
from the Orca devs on thi
list; Joanmarie Diggs
Subject: Re: [Accessibility-ia2] Fwd: text attribute range calculation
Rob, sorry I didn't get you.
The second method: combine embedded characters into one range (that's you
suggested).
The third method: every embedded characters has own range.
What is your prefere
;>
>> Thanks,
>> RG
>>
>>
>> -Original Message-
>> From: Alexander Surkov [mailto:surkov.alexan...@gmail.com]
>> Sent: Tuesday, May 18, 2010 6:04 AM
>> To: James Teh
>> Cc: IAccessible2 mailing list; Joanmarie Diggs; Rob Gallo
>>
Alexander Surkov [mailto:surkov.alexan...@gmail.com]
> Sent: Tuesday, May 18, 2010 11:13 AM
> To: Rob Gallo
> Cc: James Teh; IAccessible2 mailing list; Joanmarie Diggs
> Subject: Re: [Accessibility-ia2] Fwd: text attribute range calculation
>
> Rob, sorry I didn't get you.
>
h; IAccessible2 mailing list; Joanmarie Diggs
Subject: Re: [Accessibility-ia2] Fwd: text attribute range calculation
Hi, Rob.
Aaron suggestion was like [*plain*plain**)[bold*bold*), which I come here
with.
Your suggestion was [*)[plain)[*)[plain)[**)[bold)[*)[bold)[*).
My last suggestion (based on
all take a look and make suggestions as necessary.
>
>
>
> Thanks,
> RG
>
>
> -Original Message-
> From: Alexander Surkov [mailto:surkov.alexan...@gmail.com]
> Sent: Tuesday, May 18, 2010 6:04 AM
> To: James Teh
> Cc: IAccessible2 mailing list; Joanmarie D
urkov [mailto:surkov.alexan...@gmail.com]
Sent: Tuesday, May 18, 2010 6:04 AM
To: James Teh
Cc: IAccessible2 mailing list; Joanmarie Diggs; Rob Gallo
Subject: Re: [Accessibility-ia2] Fwd: text attribute range calculation
Hi, Jamie, Rob and all.
We should come to either solution as soon as we can. We shouldn&#x
Hi, Jamie, Rob and all.
We should come to either solution as soon as we can. We shouldn't hit
a mark by the first shoot. First of all let's figure out more
logically correct and handy solution. I'll implement it and provide
Firefox build for testing. If you and Jonaie will find performance
satisfa
Hi, Pete.
Yes, it provides wrong information. At least it's not how
IAccessibleText::caretOffset or selection works. But you're right we
assume AT should check every embed characters separately when they met
it.
Thank you.
Alex.
On Tue, Apr 20, 2010 at 7:52 AM, Pete Brunet wrote:
> Alex, give
I think I'm fine with Rob suggestion. It's even easier from
implementation point of view. And AT doesn't need to traverse the
string between offsets to find embed characters to query attributes
for it.
However please you consider to have own range for every embed characters like
[*)[plain)[*)[pla
Alex, given the string abc*def why don't you have to walk into the child
node? If the attributes are different in the child node then the AT is
getting bad information.
Or does the AT use this information only trusting that at least the abc
and def have identical attributes and that further inve
Hi, Jamie.
Yes, it affects on ATK as well. And it's worth to note that now
Firefox text attribute implementation is very slow on big documents.
So it might make sense to care about how to decrease number of calls.
I cc'ed Joanie originally but eventually her email was lost from the
thread. Cc'ing
On 17/04/2010 5:28 PM, Rob Gallo wrote:
> This issue is a tough one. I would like to suggest yet another approach
> where embed characters would have their own ranges, and those ranges should
> basically return an empty attribute string, or a string that would amount to
> plain text.
In principle,
18 matches
Mail list logo
