You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pressing "a" or shift+a to navigate by annotation says "No next/previous annotation".
In Internet Explorer, this should search for ins/del tags.
In other browsers, it should report "Not supported in this document".
I think this can be generalised to all quick navigation types that aren't supported by specific VirtualBuffers. I think this can be done by having VirtualBuffer._iterNodesByType raise NotImplementedError instead of returning an empty iterator when a type is not supported.
On a related note, BrowseModeTreeInterceptor._iterNodesByType needs to document that it can raise NotImplementedError. It should probably also do this itself instead of returning an empty iterator.
This reminds me of the fact that browse mode in Word says 'not supported' when using e for edit boxes, while there are in fact documents with edit boxes in word.
…ve to an element which isn't supported for the document, NVDA reports that this isn't supported rather than reporting that there is no element in that direction.
_iterNodesByType now always raises NotImplementedError when a type is not supported.
Re #5691.
Pressing "a" or shift+a to navigate by annotation says "No next/previous annotation".
In Internet Explorer, this should search for ins/del tags.
In other browsers, it should report "Not supported in this document".
I think this can be generalised to all quick navigation types that aren't supported by specific VirtualBuffers. I think this can be done by having
VirtualBuffer._iterNodesByType
raise NotImplementedError instead of returning an empty iterator when a type is not supported.On a related note,
BrowseModeTreeInterceptor._iterNodesByType
needs to document that it can raise NotImplementedError. It should probably also do this itself instead of returning an empty iterator.Thoughts, @michaelDCurran?
The text was updated successfully, but these errors were encountered: