Re: ARIA UAIG test case failure

I'll answer your question if you answer mine. :-)

My question was:  If the author has further explicitly declared this 
combobox as having no autocompletion, why does the <input>'s native 
autocompletion have any influence here?  The relevant markup is:

<input type="text" role="comobox" aria-autocomplete="none">

There is a difference between your example and the 
combobox/autocompletion one in that no native autocomplete attribute is 
given for the latter.  That is, the author has *not* done the following:

<input type="text" role="comobox" aria-autocomplete="none" 
autocomplete="on">

Furthermore, according to Mozilla's documentation 
(https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Input?redirectlocale=en-US&redirectslug=HTML%2FElement%2FInput):

" If the autocomplete attribute is not specified on an input element, 
then the browser uses the autocomplete attribute value of the <input> 
element's form owner."

There is no <form> element in the combobox test markup.  I'm not sure 
what is supposed to happen then; why is it automatically set to 'on'?

So, given the author has explicitly set the role to "combobox" and 
aria-autocompletion to "none", and not specified anything for the native 
autocompletion attrtibute, they still get auto-completion nonetheless?  
Is this true for all browsers?  That is, is this interoperable behaviour?

If that is the state of the world, then I guess the author has to forego 
using aria-autocomplete where they use <input> elements and make sure 
they set the native autocompletion as appropriate. Still, the 
aria-autocomplete attribute is richer than the native. The native has 
but on/off states.  ARIA provides for inline, list, and both kinds of 
completion.  What happens in the following case? Is it a dropdown list, 
even if the author has programmed an inline completion scenario?

<input type="text" role="combobox" aria-autocomplete="line">

One minor issue:  the native autocompletion attrtibute is an HTML5 
addition.  The combobox test file is explicitly declared HTML 4.01 
transitional.  I suspect this is moot, however, and that FF "promotes" 
the markup and treats is as HTML5.

-- 
;;;;joseph.


'A: After all, it isn't rocket science.'
'K: Right. It's merely computer science.'
              - J. D. Klaun -

Received on Tuesday, 15 October 2013 18:33:37 UTC