There is a set of AX.*SearchKey's used for content navigation that don't have anything to do with making content appear in rotor. We should support them to allow for better content navigation. From what I can gather, they are as follows: - AXBlockquoteSameLevelSearchKey - AXBlockquoteSearchKey - AXBoldFontSearchKey - AXDifferentTypeSearchKey - AXFontChangeSearchKey (Chrome doesn't do this) - AXFontColorChangeSearchKey (Chrome doesn't do this) - AXGraphicSearchKey - AXHeadingLevelXSearchKey (1-6) - AXHighlightedSearchKey (Chrome doesn't do this) - AXKeyboardFocusableSearchKey - AXItalicFontSearchKey - AXMisspelledWordSearchKey (Chrome doesn't do this) - AXOutlineSearchKey - AXPlainTextSearchKey - AXSameTypeSearchKey - AXStyleChangeSearchKey (Chrome doesn't do this) - AXTableSameLevelSearchKey (Chrome doesn't do this) - AXUnderlineSearchKey
Bug 1666606 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
There is a set of AX.*SearchKey's used for content navigation that don't have anything to do with making content appear in rotor. We should support them to allow for better content navigation. From what I can gather, they are as follows: - AXBlockquoteSameLevelSearchKey - AXBlockquoteSearchKey - AXBoldFontSearchKey - AXDifferentTypeSearchKey - AXFontChangeSearchKey (Chrome doesn't do this) - AXFontColorChangeSearchKey (Chrome doesn't do this) - AXGraphicSearchKey - AXHeadingLevelXSearchKey (1-6) - AXHighlightedSearchKey (Chrome doesn't do this) - AXKeyboardFocusableSearchKey - AXItalicFontSearchKey - AXMisspelledWordSearchKey (Chrome doesn't do this) - AXOutlineSearchKey - AXPlainTextSearchKey (Chrome doesn't do this) - AXSameTypeSearchKey - AXStyleChangeSearchKey (Chrome doesn't do this) - AXTableSameLevelSearchKey (Chrome doesn't do this) - AXUnderlineSearchKey