GNOME Bugzilla – Bug 463783
Orca cannot provide reliable access to HTML content effective 4th August FF3 build
Last modified: 2007-08-14 12:28:28 UTC
This is a tracking bug for the following Mozilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=391023 getCharacterExtents() is returning values based on source rather than document content There used to be a bug in Firefox that was causing whitespace characters from the HTML source to be exposed as actual text. The fix in that bug apparently did not include a corresponding change in what is returned by text.getCharacterExtents(). It would seem that text.getText() now returns text from the document content, but text.getCharacterExtents() returns extents based on the characters in the source. As a result, the presence of whitespace characters in the document source completely mess up the extents. We rely upon having valid extents; without them, we're pretty much hosed. Orca users should not use Firefox from 4th August or later until this gets resolved.
The above bug has been marked as fixed. Verified. Unfortunately, here's another bogus extents bug that seems to have resulted from the whitespace fix: https://bugzilla.mozilla.org/show_bug.cgi?id=391991 getCharacterExtents() is returning (0, 0, 0, 0) for text that is not on the first line of an HTML object.
The bug in Comment #1 has just been fixed. I did a cursory test and things seem back to normal in both Firefox and Thunderbird. Closing this one out as NOTGNOME.