6756 2009-04-02 16:32:33 +0000 3.6.2 what kind of errors are to be reported for invalid aria attribute values? 2009-09-15 16:29:48 +0000 1 1 1 Unclassified ARIA Core AAM 1.0 All All RESOLVED FIXED P1 normal Last Call 1 dbolter andi.snowweaver andi.snowweaver aria-ua-impl oldest_to_newest 24512 0 dbolter 2009-04-02 16:32:33 +0000 This action item came out of the March 20 UAI TF meeting. 24516 1 dbolter 2009-04-02 17:14:03 +0000 What kind of error reporting were we talking about here? Was it browser console output like "invalid aria-valuenow", or was it something like reporting a -999 for invalid values (through platform API)? 24538 2 dbolter 2009-04-03 16:24:41 +0000 I guess the related question is what to return if the aria-valuenow is missing (where is shouldn't be missing). 24539 3 dbolter 2009-04-03 16:32:25 +0000 From today's call: Investigate using a null value. Is there value in raising an event? 25078 4 andi.snowweaver 2009-05-08 18:08:06 +0000 *** Bug 6885 has been marked as a duplicate of this bug. *** 25080 5 andi.snowweaver 2009-05-08 18:09:15 +0000 Cynthia to ask the IE guys what browsers should do in this case David to find out what Mozilla team does 25519 6 andi.snowweaver 2009-06-09 01:20:20 +0000 From Cynthia via e-mail: "Don't use -999 type errors in the API, because these features are too generic to be sure that -999 (or any value) is always wrong. Error reporting should be done through a console. We still need to design that, but I don't think it's a p1 feature." I think we need more here. Seems weird to say what error shouldn't be returned without saying what should be returned. Keeping this one open for the next editor's draft. 25718 7 andi.snowweaver 2009-06-26 15:27:44 +0000 06/26/09: No error through API. User agents may return an error through a debug console. 27195 8 andi.snowweaver 2009-09-15 16:29:48 +0000 Re-opened in error.