To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=81718
------- Additional comments from [EMAIL PROTECTED] Thu Oct 18 14:40:24 +0000 2007 ------- > you will refine the AT-SPI API specification and I will check, what > can be done in the UNO accessibility API and in the accessibility > bridge for the mapping of the AT-SPI API to the UNO accessibility API. Agreed, but the difference is that it will be possible for you to support the new behavior much much sooner since it doesn't require any new API. All it's doing is extending the interpretation of an existing API. Given the variance in the AT-SPI implementations we see all the time across Java, OOo, FF, and GTK, I also think it is probably OK for you to go ahead with this change without requiring the specification to be strictly enhanced to include this. For the API enhancement, I've opened the following support reqeust for AT-SPI: http://bugzilla.gnome.org/show_bug.cgi?id=487918. Please let me know how your investigation goes. If it's possible for you to do this sooner than later, it would be great. > Is it ok for everybody, if I change the issue type to "enhancement" and > change the issue summary to "[a11y] OOo Writer should report run attributes > for the end position of a paragraph"? This would be more accurate. Thanks! --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
