Jamie asked if Mozilla could enhance their support for the "formatted" object attribute, i.e. rename it to "display" and instead of just using the value "block", also use the full set of CSS2 values.
Mozilla is implementing IAEditableText on just about everything, e.g. combo box
The following was received from Aaron Levanthal:
Basically anything can become editable in the DOM, We never know ahead of time what mutations an author will case.
Because the rules of COM say that the interfaces supported on an object must be static during the object's lifetime, we have 2 choices:
Support every interface and use states or other things to show if the interface matters
Tear down and create a new object when it needs to support a different interface
The Orca folks asked for us to lean toward #1, because it was harder to deal with objects being destroyed and recreated.
That said, I'm not sure that combobox would ever be editable itself. It might have an editable child. So that particular case might be a bug. But in general, check IA2_STATE_EDITABLE to see if something is really edtiable.
Pete pointed out that IAEditableText has the copyText method so it might make sense to implement the interface on non-editable text.
Jamie will followup via email.
IA2::scrollTo - add an enum value not limited to an edge or corner
Alexander Surkov pointed out via email that FF3 already has SCROLL_TYPE_ANYWHERE. IA2 could add the same constant.
David Bolter suggested that we might also want a constant that causes the object and all its containing objects to be scrolled into view.
Old NVDA items
Last year NVDA raised some issues which really are larger ATK/IA2 issues. We think these issues were raised via the Open A11y group in January. Jamie will review these issues to see if those are the issues he is referring to. Also, it was suggested that these could be reopened and discussed with Willie and Li Yuan at a call convenient to the US, China, and Australia.