This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8464 - spinbutton: PF Issues 86 & 87
Summary: spinbutton: PF Issues 86 & 87
Status: RESOLVED FIXED
Alias: None
Product: ARIA
Classification: Unclassified
Component: Core AAM (show other bugs)
Version: 1.0
Hardware: PC Windows XP
: P1 normal
Target Milestone: ---
Assignee: Andi Snow-Weaver
QA Contact: ARIA UA Implementors
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-08 22:13 UTC by Andi Snow-Weaver
Modified: 2010-06-29 16:34 UTC (History)
1 user (show)

See Also:

Attachments

Comment 1 Andi Snow-Weaver 2010-02-09 16:39:16 UTC 
David to take these issues to the ARIA TF.
Comment 3 Andi Snow-Weaver 2010-03-02 15:35:53 UTC 
So David, what is the resolution?
Comment 4 David Bolter 2010-03-02 16:26:03 UTC 
Issue 86: How to handle cases where spinners have no minimum, or no maximum, nor both

IAccessible2: FF currently exposes 0.
MSAA: FF currently exposes "".
ATK: FF currently exposes 0.

Issue 87: How to set the aria-valuenow property for spinbutton when unknown.

IAccessible2: FF currently exposes 0.
MSAA: FF currently exposes "".
MSAA: FF currently exposes 0.

What does IE currently do?
Comment 5 David Bolter 2010-03-02 18:35:44 UTC 
Oh hmmm we use VT_EMPTY... let me double check...
Comment 6 Andi Snow-Weaver 2010-04-21 21:18:32 UTC 
David, what should we put in the table in the Author Errors section? 

It currently has "0" for valuemax and valuemin. And what about valuenow?

Are these the values used for sliders as well as spinbuttons?
Comment 7 David Bolter 2010-04-22 01:16:46 UTC 
"0" for valuenow as well, yes. Same for sliders and spin buttons, if I recall correctly; and it makes sense to be consistent.