GNOME Bugzilla – Bug 618806
WhereAmI in Thunderbird presents the full message text when a message is editable
Last modified: 2010-09-20 10:52:57 UTC
(From the Orca list) Hy List, I see an interesting problem with Thunderbird composing message or reply a message if I using Orca where am I command: If I write more lines with message body and press where am I command, Orca reads entire message body text. I see this problem with Orca git master version and Thunderbird 3.0.4. The reproducation test is very easy: 1. Launch Thunderbird, and press for example Ctrl+n key combination. 2. Temporary fill in the to: and subject: fields, and write some lines at the message body text. 3. Press where am I command if you done the some line typing. If this problem is present for example the Orca 2.30.1 version, you hear entire message body text. Anybody confirming this problem? This problem already reported in Bugzilla? If not, and anybody confirming this bugy working method and this is absolute an Orca related bug, I welcome make a report and attaching a debug.out file. Attila
Confirmed.
Created attachment 161181 [details] [review] proposed fix This patch adds a new Thunderbird-specific formatting.py into Orca to handle the document frame. To test, be sure to start with configure/autogen.sh.
(In reply to comment #2) > Created an attachment (id=161181) [details] [review] > proposed fix > > This patch adds a new Thunderbird-specific formatting.py into Orca to handle > the document frame. To test, be sure to start with configure/autogen.sh. Works fine when composing a message but when reading a received message exhibits strange behavior. To reproduce try the following steps: 1. open an old message. 2. Go to the first line of the message. 3. Press orcaKey+return. Orca should read the contents of the first line as expected. 4. Move to the second line pressing the down key and repeat the step 3. Instead of read the content of the second line, orca reads the content of the first line.
Confirmed. Seems to be the same without the patch. Looks like a different bug to me. Are you seeing this problem only with the patch attached to this bug?
And since the problem only seems to occur when you do one whereAmI and then a second, it seems to be a caching issue; not a formatting string issue.
(In reply to comment #4) > Confirmed. Seems to be the same without the patch. Looks like a different bug > to me. Are you seeing this problem only with the patch attached to this bug? No, the same problem without the patch.
And I've since reproduced the problem in Firefox. So it's definitely a bug, it's definitely caching-related, and it's Gecko rather than Thunderbird. I'll open a new bug for that. Please let me know when you've beaten on the patch for this particular bug sufficiently to make it commit-worthy (assuming no other issues are found). Thanks!
(In reply to comment #7) > And I've since reproduced the problem in Firefox. So it's definitely a bug, > it's definitely caching-related, and it's Gecko rather than Thunderbird. I'll > open a new bug for that. > > Please let me know when you've beaten on the patch for this particular bug > sufficiently to make it commit-worthy (assuming no other issues are found). > Thanks! No more problems found. I think that it can be applied.
Comment on attachment 161181 [details] [review] proposed fix http://git.gnome.org/browse/orca/commit/?id=b73a3ade06869716abfd0d3b1a7d822f67ce234e
Thanks José! Committed to master. The other issue was a one line fix (bug 618827) which has been committed to both master and the gnome-2-30 branch. Nice catch on that one! Marking as 2.30.2? for consideration once we get closer to the next stable release.