RE: ACTION-1490 proposal says good bye to the "inline" notion for combobox

Sorry about that, I got this part confused with another thread.

My point was in regard to the section 5.6.3 Relations at
https://www.w3.org/TR/core-aam-1.1/#h-mapping_additional_relations

Where it states:

Often in a GUI, there are relationships between the widgets that can be exposed programmatically to assistive technology. WAI-ARIA provides several relationship properties which are globally applicable to any element: aria-controls, aria-describedby, aria-flowto, aria-labelledby, aria-owns, aria-posinset, and aria-setsize. Therefore, it is not important to check the role before computing them. User agents can simply map these relations to accessibility APIs as defined in the section titled State and Property Mapping.

-----Original Message-----
From: Joseph Scheuhammer [mailto:clown@alum.mit.edu] 
Sent: Wednesday, February 17, 2016 12:05 PM
To: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>; Rich Schwerdtfeger <richschwer@gmail.com>
Cc: Matt King <mck@fb.com>; ARIA Working Group <public-aria@w3.org>
Subject: Re: ACTION-1490 proposal says good bye to the "inline" notion for combobox

On 2016-02-16 2:45 PM, Bryan Garaventa wrote:
> Thanks, I understand the logic, especially regarding event bubbling. However in all the tests I've done, I don't remember ever seeing this work where an owned element passed events up to its parent if it wasn't a direct child already.

I'm confused, since I wasn't saying anything about event bubbling. I was discussing a mandated procedure for setting the AAPI focusable state on possible active descendants.

--
;;;;joseph.

'Die Wahrheit ist Irgendwo da Draußen. Wieder.'
                  - C. Carter -

Received on Wednesday, 17 February 2016 20:51:35 UTC