https://bugs.documentfoundation.org/show_bug.cgi?id=170274
Michael Weghorn <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTOURBUG Status|NEEDINFO |RESOLVED --- Comment #4 from Michael Weghorn <[email protected]> --- (In reply to Joanmarie Diggs from comment #3) > This used to work in Orca. Not by paying attention to shortcuts, but by > paying attention to the toggle button state change. (Eventually Orca will > pay attention to the actual attributes that change, but I've not gotten to > that.) > > I'll update Orca to get the toggle button presentation working again. Great, thanks a lot! Closing this as NOTOURBUG here then. FYI: When I implemented this for NVDA and thought about making use of text attributes instead of toggle button state etc., I ran into the problem that there isn't necessarily any actual text whose text attributes could be used/. Quoting from my commit message in https://github.com/nvaccess/nvda/commit/46a343685247ed7d1adfb737716590ec4be456a0 : "Note: An alternative approach querying the text attributes from the IAccessibleText interface instead of the button state would run into the problem that it works reliably when text is selected, but has no clear way to figure out whether or not bold is enabled or not when there's no selection. (The text attributes need to be queried for a given index, but when the text cursor is e.g. in front of the first character of non-bold text, Ctrl+B would enable bold for newly typed text, but querying the text attributes at index 0 of the existing text would still not report bold, resulting in issues like as observed and described in issue #16412 for MS Word.)" -- You are receiving this mail because: You are the assignee for the bug.
