After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 593520 - The Gecko script's getBottomOfFile needs to be more efficient
The Gecko script's getBottomOfFile needs to be more efficient
Status: RESOLVED FIXED
Product: orca
Classification: Applications
Component: general
2.27.x
Other All
: Normal normal
: 2.28.1
Assigned To: Joanmarie Diggs (IRC: joanie)
Orca Maintainers
Depends on:
Blocks: 404403
 
 
Reported: 2009-08-30 01:46 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2009-09-24 23:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Attachments
fix (1.06 KB, patch)
2009-08-30 01:54 UTC, Joanmarie Diggs (IRC: joanie)
committed Details | Review

Description Joanmarie Diggs (IRC: joanie) 2009-08-30 01:46:46 UTC
Right now the Gecko script's getBottomOfFile method looks for the last object and then uses findNextCaretInOrder to move from the last object to the last character. This allows us to deal with the various and sundry goofiness we encounter in web content. Unfortunately, however, if the last embedded object character is many characters away from the last character in the document frame, pressing Control End while Orca is controlling the caret will result in a very long wait. :-(
Comment 1 Joanmarie Diggs (IRC: joanie) 2009-08-30 01:54:39 UTC
Created attachment 142009 [details] [review]
fix

This patch adds an initial check to getBottomOfFile: If the last character in the document frame is not an embedded object character, we return the document frame and the offset of that last character. This solves the problem of the test case, is pylinted, and fully regression tested.

Because we've branched for 2.28, I've committed this patch to master (and only master) so that it will get tested by our bleeding-edge users. Assuming it doesn't have any unforeseen side effects, we should consider including this for 2.28.1.
Comment 2 Joanmarie Diggs (IRC: joanie) 2009-08-30 01:57:26 UTC
In order to track bugs/fixes which we want to keep in mind for 2.28.1 without having to keep all of those bugs open and in limbo until then, I'm going to start adding "2.28.1?" to the whiteboard.
Comment 3 Joanmarie Diggs (IRC: joanie) 2009-09-24 23:32:39 UTC
Now that code freeze is over, I've committed this fix to the gnome-2-28 branch
for inclusion in 2.28.1