Hi Jamie, It's a good question. I don't think we've ever discussed when a method should be added vs an object attribute. It seems like we have gotten what is truly needed via methods and object attributes come along as needed between releases, when it's simply an atribute, and when it's not such a central issue that the attribute should be a method. And it seems like isNamePreffered (or isNamePrefferedOverText) fits into the "it could be an attribute" category.
How pressing is the need for this feature for you? The Firefox team would like to get the new IA2 release ready for late Summer, early Fall and I think that is possible. I think we've come to decisions about everything and I need to document those once more, in a single post, for a final review and the code up the revised IDL for another review. Hopefully that won't be too much of an effort. I'm in the middle of starting up a project and so it's been consuming, but I'll try to get the documentation mentioned above out on this list fairly soon. Pete On 7/24/12 7:21 PM, James Teh wrote: > Hi Pete, > > Oops! Not sure how I missed that. Thanks for the correction. > > Regarding whether to use an object attribute, I guess the question is > when object attributes should be used. The answer so far seems to be > that they are used when the information isn't absolutely essential; > e.g. an AT can't cope without role and name, but it can cope without > knowing about list or paragraph formatting. It's probably also fair to > say that we don't want to expose long or complex values via > attributes; e.g. the original proposal of exposing the actual name in > explicitName wouldn't have been suitable, as it could have been quite > long. However, I'd think boolean values are fine and avoid introducing > new methods. The only issue in this case is that the name might need > to be changed to something like isNamePrefferedOverText. > > Thoughts? > > Jamie > > On 25/07/2012 3:54 AM, Pete Brunet wrote: >> Hi Jamie, The latest post is actually a little later on July 26 and can >> be seen at: >> http://lists.linuxfoundation.org/pipermail/accessibility-ia2/2011-July/001515.html >> >> You agreed with this 5 days later at: >> http://lists.linuxfoundation.org/pipermail/accessibility-ia2/2011-July/001515.html >> >> >> I'm open to discussion of whether or not to use an object attribute >> though. >> >> Pete >> >> On 7/24/12 12:14 AM, James Teh wrote: >>> Hi all, >>> >>> Unless I'm missing something, the last message I can find about the >>> explicit name proposal is here: >>> http://lists.linuxfoundation.org/pipermail/accessibility-ia2/2011-July/001509.html >>> >>> >>> I explained there why I prefer the approach of using a flag rather >>> than having a separate name property. >>> >>> If others agree with the flag, is there any reason this shouldn't just >>> be done using an object attribute, rather than introducing another >>> method? With the new object attribute retrieval method, this will be >>> just as efficient. >>> >>> The other benefit to this is that it also allows us to start using it >>> right away. This is definitely something that is needed. >>> >>> Thanks, >>> Jamie >>> >> >> -- >> *Pete Brunet* >> >> a11ysoft - Accessibility Architecture and Development >> (512) 467-4706 (work), (512) 689-4155 (cell) >> Skype: pete.brunet >> IM: ptbrunet (AOL, Google), [email protected] (MSN) >> http://www.a11ysoft.com/about/ >> Ionosphere: WS4G > -- *Pete Brunet* a11ysoft - Accessibility Architecture and Development (512) 467-4706 (work), (512) 689-4155 (cell) Skype: pete.brunet IM: ptbrunet (AOL, Google), [email protected] (MSN) http://www.a11ysoft.com/about/ Ionosphere: WS4G
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
