User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20061208 Minefield/3.0a1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20061208 Minefield/3.0a1 The accessible text implementation provides a setCaretOffset method to set the caret position. For Firefox, I believe this should help an assistive technology to write its own caret navigation mechanism. For the most part (modulo some other bugs already logged), this method kind of works. However, I notice that when setting the caret position to something off the screen, the page does not scroll the caret position into view. It would be great if the Firefox accessibility implementation could provide this. Reproducible: Always
Component: Disability Access → Disability Access APIs
Product: Firefox → Core
Version: unspecified → 1.0 Branch
Assignee: nobody → aaronleventhal
QA Contact: disability.access → accessibility-apis
Version: 1.0 Branch → Trunk
I confirm we need this functionality to do caret browsing. I'm not sure whether setCaretOffset is the correct API to do this.
Status: UNCONFIRMED → NEW
Ever confirmed: true
nsISelectionController::ScrollSelectionIntoView seems we can use it
Created attachment 249669 [details] [diff] [review] patch for willie this patch can scroll the text into view when setCaretOffset is called. you can use it as a tmp solution for your work.
(In reply to comment #3) > Created an attachment (id=249669) [details] > patch for willie > > this patch can scroll the text into view when setCaretOffset is called. you can > use it as a tmp solution for your work. Yeah and thanks! Is this something that will find its way into a nightly build (I've yet to be able to successfully build Firefox from sources :-()?
aaron, any comments here?
Comment on attachment 249669 [details] [diff] [review] patch for willie I don't see a problem at all, and I believe it to be correct. This is currently how one scrolls to a word in AT-SPI -- by setting the caret or selection.
Attachment #249669 - Flags: review+
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.