Just today I have uploaded patches to this bug:
https://bugzilla.gnome.org/show_bug.cgi?id=684576
that do a refactoring of AtkValue. One of the main objectives is
including a text description for values, and include the support for ranges.
Any feedback is welcome
Best regards
On 12/11/2013 06:1
I'd say ARIA extension makes sense but I have a feeling that standard ways
can be used here like changing the accessible description or using the live
regions.
Thanks.
Alex.
On Fri, Dec 20, 2013 at 12:29 PM, Piñeiro wrote:
>
> On 12/19/2013 11:15 PM, Jason White wrote:
> > Mario Sanchez Prada
On 12/19/2013 11:15 PM, Jason White wrote:
> Mario Sanchez Prada wrote:
>> From the point of view of the implementation, it should not be an issue to
>> expose those optimal, low and high values in WebKit (besides adding some
>> bits in WebCore’s a11y layer). The tricky thing will be of course ge
Mario Sanchez Prada wrote:
> From the point of view of the implementation, it should not be an issue to
> expose those optimal, low and high values in WebKit (besides adding some
> bits in WebCore’s a11y layer). The tricky thing will be of course getting
> the textual representation of the value d
Hi all,
I know I‘m late to the discussion, but I would like to show my support for
expanding the AtkValue interface. Furthermore, it’s not the first time I found
a situation where having a more complete version of the AtkValue interface
would be handy (see [1] and [2]), and this element seems l
Hi, Joanie. I'm fine to go with any reasonable approach, anything that
helps you to expose widget features. If that's value interface then let's
do it. If states then I'm fine with it and agree to follow expected routine
like fire state change events. If we talk about state constants naming then
op
Hey Alexander, all.
On 12/13/2013 07:41 PM, Alexander Surkov wrote:
> Said above can be applied to wrong value which is exposed as invalid
> state but nevertheless it's a state. So I don't see a semantical
> contradiction here. If the value is optimal then control is in optimal
> state.
On this
On Fri, Dec 13, 2013 at 01:41:30PM -0500, Alexander Surkov wrote:
> Hi, Joanie. Answering inline.
>
>
> On Fri, Dec 13, 2013 at 11:41 AM, Joanmarie Diggs wrote:
>
> On 12/12/2013 04:12 PM, Alexander Surkov wrote:
>
> > I'm ok with AtkValue extension, it makes sense if Orca wants comple
Hi, Joanie. Answering inline.
On Fri, Dec 13, 2013 at 11:41 AM, Joanmarie Diggs wrote:
> On 12/12/2013 04:12 PM, Alexander Surkov wrote:
>
> > I'm ok with AtkValue extension, it makes sense if Orca wants complete
> > information about the control.
>
> Exactly how Orca is going to provide this i
On 12/12/2013 04:12 PM, Alexander Surkov wrote:
> I'm ok with AtkValue extension, it makes sense if Orca wants complete
> information about the control.
Exactly how Orca is going to provide this information is something I am
still considering. But potentially, yes, Orca is going to want this
info
Hi, Alejandro. Answsering inline.
On Thu, Dec 12, 2013 at 6:53 AM, Piñeiro wrote:
> Hi Alexander.
>
> As alluded to in our response yesterday, we have a couple of issues (in
> addition to the one you raised) related to AtkValue which need to be
> resolved:
>
> 1. AT-SPI2 (and Orca) expect values
Hi Alexander.
As alluded to in our response yesterday, we have a couple of issues (in
addition to the one you raised) related to AtkValue which need to be
resolved:
1. AT-SPI2 (and Orca) expect values as doubles; ATK, however, allows GValues
2. There is no way to get the on-screen description of
Hi Alexander,
Thanks for pointing out this new element. We are right now at the
WebkitGTK2013 hackfest, so Joanie and I had some time to discuss this.
After giving this some thought, we think that a state is not the proper
way to go. It would be better to expose this by expanding the AtkValue
inte
13 matches
Mail list logo
