When typing a message in Outlook 2003 letters get mixed up #2953

Closed
nvaccessAuto opened this Issue Jan 30, 2013 · 11 comments

2 participants

@nvaccessAuto

Reported by heikofolkerts on 2013-01-30 17:12
I know this sounds really strange but I can't help it.
When I write an email in Outlook 2003 (running with lates NVDA under windows XP) my input gets mixed. It seems that letters are placed in other positions than they were typed. At first I thought I got some kind of legasteny but writing a mail with JAWS or with NVDA in Outlook 2010 produces correct input.

It seems that the problem occures when typing quite rapidly (and the system is quite slow). It also seems to me that the errors get more and more as the running paragraph gets longer.

The effect is so massive, that I can't really use NVDA to write mails in Outlook 2003.

Blocking #4499, #5142

@nvaccessAuto

Comment 1 by jteh on 2013-01-30 20:58
Are you using Braille? Does this occur if you avoid using the backspace key? (I realise this is unreasonable in normal situations, but please try writing without using backspace for testing purposes.)

@nvaccessAuto

Comment 2 by heikofolkerts on 2013-01-31 15:48
Yes, I am using braille. A handytech braille display to be precise. I'll try testing without backspace and report.

@nvaccessAuto

Attachment mailtyping.ahk added by heikofolkerts on 2013-02-05 10:32
Description:
Autohotkey script that uses the problem by using a single backspace to mess up the typing

@nvaccessAuto

Comment 3 by heikofolkerts on 2013-02-05 10:35
The problem is indeed caused by using a backspace. The attach autohotkey script using www.autohotkey.com demonstrates that things get messed up. Running the script in e.g. notepad shows that everything is typed correctly. Removing the backspace in the scripts makes the text apear in outlook OK.

@nvaccessAuto

Comment 4 by heikofolkerts on 2014-07-07 18:45
The same effect now occures when using Outlook 2010 with NVDA. I can reproduce the problem either on windows 7 64bit, windows 8.1 64bit and I think also under windows XP. The mixing takes place only in the subject line and the first character is exchanged by one typed later in the text. It seems that there are more mixings when the subject gets longer. The mixing occures in every mail when the subject is longer than two or three words. So I allways have to check the subject line and correct it.

I fact I often sent mails with crunched subject line to the Dev mailinglist because I forgot to correct the subject line.

Sometimes the effect is also visible in the to field but not so often.

I hope that someone can reproduce the behaviour and that we can find a fix soon because its really annoying and dangerous to send mails with a kind of nonsense subject. In the mail text this mixing doesn't occure under Outlook 2010.

@nvaccessAuto

Comment 5 by jteh on 2014-07-08 07:53
While I haven't actually reproduced this, I understand what's going on. NVDA passes keys that don't require special functionality in NVDA straight through to Windows; e.g. letters and numbers. However, we have to intercept backspace and re-send it ourselves so that we can speak the character that was erased. Unfortunately, this has to wait until NVDA is finished performing other tasks, including braille rendering. In Word/Outlook, braille rendering is relatively slow, so backspace gets handled too late.

We still haven't come up with a good way to solve this. Hopefully, we can speed up braille rendering, although we don't know how yet. Failing that, we'll have to find some way to make sure these keys don't get handled out of order.

As a matter of interest, while impractical for daily usage, does this improve if you disable everything in NVDA's document formatting settings?

@nvaccessAuto

Comment 6 by heikofolkerts on 2014-07-08 17:48
Turning off all check boxes in the document formatting dialog seems to make the mixing disappear. In my case there was only the announcement of spelling errors checked and the page switching and all announcements of HTML elements were turned on. Turning the spell checking on alone didn't seem to provocate the error - spell checking is a nice and helpful feature when typing mails.
Turning the settings on as they were before the test seemed to make the error occure more often. Sorry for the vague description but I haven't found out a way to reproduce it clearly.

@nvaccessAuto

Comment 8 by PhDoreNVDA on 2015-06-04 13:10
Reproduced with Window7 32-Bits and Outlook 2010.
to/cc/ci fields looks more sensible than others on Dell Latitude E6220 equipped with Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz 4,00 GB memory.

@nvaccessAuto

Comment 9 by jteh on 2015-06-05 04:19
Potential solution described in ticket:4499#comment:2.
Changes:
Milestone changed from None to 2015.3

@nvaccessAuto

Comment 10 by Michael Curran <mick@... on 2015-06-22 04:50
In [46d0a2e]:
```CommitTicketReference repository="" revision="46d0a2e10da911e53ed2e44d3e6839f45e4339d6"
Merge branch 't2953' into next. Incubates #2953

Changes:
Added labels: incubating
@nvaccessAuto

Comment 12 by James Teh <jamie@... on 2015-07-10 04:26
In [7b7823c]:
```CommitTicketReference repository="" revision="7b7823c71f446435d195eb9f9a5037411c9c407c"
Fix garbled text when typing in Outlook with braille enabled and with text expansion functionality (e.g. in AutoHotkey).

InputGesture.execute: if an intercepted command script (script that sends the gesture it intercepts) is queued and or has not yet completed its execution, queue any further gestures that do not have a script via a fake script that just sends the gesture. this ensures that input stays in order even if it was delayed by NVDA.
Fixes #2953, #4499.

Changes:
Removed labels: incubating
State: closed
@jcsteh jcsteh was assigned by nvaccessAuto Nov 10, 2015
@nvaccessAuto nvaccessAuto added this to the 2015.3 milestone Nov 10, 2015
@michaelDCurran michaelDCurran added a commit that referenced this issue Nov 23, 2015
@michaelDCurran michaelDCurran Fix garbled text when typing in Outlook with braille enabled and with…
… text expansion functionality (e.g. in AutoHotkey).

InputGesture.execute: if an intercepted command script (script that sends the gesture it intercepts) is queued and or has not yet completed its execution, queue any further gestures that do not have a script via a fake script that just sends the gesture. this ensures that input stays in order even if it was delayed by NVDA.
Fixes #2953, #4499.
7b7823c
@jcsteh jcsteh added a commit that referenced this issue Nov 23, 2015
@jcsteh jcsteh Actually, the fix for garbled characters with Outlook and braille (#2953
) doesn't fix garble keys with text expansion functionality (#4499) after all. :(
b6a4273
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment