When focusing and typing in URL bar, only "CBO Location" is read by gnopernicus. The content in URL bar and the actions in URL bar (typing and selecting) are not read by gnopernicus. The accessible for URL bar is designed to be "Combo Box" on Unix, which makes URL bar is not accessible.
Will -- is this problem visible with Orca in current nightly builds? Or should this be closed.
I see some oddities with Orca and the location bar, but typing and navigating seem to speak. This particular bug is for Gnopernicus, though, so maybe it's not getting the events it needs?
If I move the focus from the URL bar to the next object from the window and then I go back to the URL bar (Shift+Tab), the URL address is selected, but not reported by Gnopernicus.
os@baum (sorry don't know your name) -- what should ATSPI be telling you differently? What are you asking us to fix?
The problem is that AccessibleText_getTextAtOffset returns 0 for both startOffset and endOffset (for line start and line end) in the case presented in comment #3.
Mike, I think you'll need to run Gnopernicus and watch what happens in the getTextAtOffset call that happens when you shift+tab back to the URL bar. Why is it returning 0 for endOffset -- presumably it should be returning the end of the line for that.
Yes. I have installed gnopernicus on my fc5 box and am debuging.
Mike, what's the progress report on this one?
Hi, firstname.lastname@example.org, nsAccessibleEditableText::GetTextAtOffset() is not called when I move the focus to url bar with gnopernicus opened. "Tool bar" is read. nsAccessibleText::GetTextAtOffset neither, I guess you mean nsAccessibleEditableText in comment#5?
Removing from dependency list for Firefox 2.
When move the focus to url bar, AccessibleText_getTextAtOffset is called by get_text_range_from_offset() function from gnopernicus/srlow/libsrlow/SRObject.c file. The start_range and end_range values for AccessibleText_getTextAtOffset are 0 in this case, which is not ok since the line end of the selected text from the url bar is bigger than 0.
email@example.com -- are you set up to be able to debug where the call dies? Do you build the atk/at-spi infrastructure code? We're not getting the gettextatoffset call in Mozilla.
os@baum -- is this still a problem?
I'm not sure why this is marked as blocking Orca. os@baum -- is this still a problem for you in Firefox 3 builds? http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
This bug is not reproducible any more, it works fine for me.