Closed Bug 2012252 Opened 5 months ago Closed 3 months ago

Windows11 has issues with the Text Cursor Indicator, often staying on the left side of the current line in the Compose Windows

Categories

(Core :: Disability Access APIs, defect)

Unspecified
Windows
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr115 --- unaffected
firefox-esr140 --- disabled
firefox147 --- wontfix
firefox148 --- fix-optional
firefox149 --- fix-optional

People

(Reporter: kevin.mcgrail-mozillabugzilla, Unassigned)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: nightly-community, regression, Whiteboard: [uiaFastFollow])

Steps to reproduce:

I've used the text cursor indicator feature in Windows 10 and Windows 11. Upgraded to a new machine (going from W10 to W11) and when I am working in the composition window, the text cursor indicator acts erratically.

It worked perfectly on my Windows 10 machine and it works correcting in the To/CC/BCc/Subject areas.

Actual results:

Sometimes the text indicator works for the first line. But more often it just stays stuck on the left in the column 0 on the current line while the text is being typed and going to the right. If I go up and down in the composition window, the text indicator goes up and down but stays on the left side.

I have tried the accessibility.force disabled option as well as different email format options like HTML only as well as removing my signature and starting a blank composition window.

Expected results:

The text indicator should be right with the cursor as you move the cursor either with the arrow keys, pgup/dn, typing, etc.

Setting accessibility.uia.enable to 0 solves the issue on TB148.0beta.

Status: UNCONFIRMED → NEW
Ever confirmed: true
Blocks: 1993152

Confirming for my machine that setting accessibility.uia.enable to 0 (from 2) in TB 147.0 release also seems to be acting much better as well. -KAM

OS: Unspecified → Windows
Summary: Composition Window on Windows11 has issues with the Text Cursor Indicator often staying on the left side of the current line in the Compose Windows → Windows11 has issues with the Text Cursor Indicator, often staying on the left side of the current line in the Compose Windows
Version: Thunderbird 147 → Thunderbird 139

Jamie, any advice?

Flags: needinfo?(jteh)

Are there simple steps that reproduce this 100% of the time? For example, if you just start with a blank composer (no signature), can you reproduce it by just typing a single character, pressing enter, then typing another character on the second line, or does it require more complicated text than that?

Do you use Firefox? if so, please paste this URL into the address bar. Are you available to reproduce it with this simple text box?

data:text/html,<div contenteditable>editable text goes here</div>

Alternatively, try this:

data:text/html,editable text goes here<script>document.designMode = "on";</script>

The reason I ask about Firefox is that it's much easier for our team to diagnose and fix this if we can pin it down to a test case in Firefox.

Flags: needinfo?(jteh) → needinfo?(kevin.mcgrail-mozillabugzilla)
Blocks: uiatext
No longer blocks: 1993152
Severity: -- → S3
Component: Disability Access → Disability Access APIs
Product: Thunderbird → Core
Version: Thunderbird 139 → unspecified
See Also: → 2012651

(In reply to James Teh [:Jamie] from comment #5)

Are there simple steps that reproduce this 100% of the time? For example, if you just start with a blank composer (no signature), can you reproduce it by just typing a single character, pressing enter, then typing another character on the second line, or does it require more complicated text than that?

  1. From account settings, you should turn Compose messege in HTML format to on
  2. Open composition window (html mode without any signature. i.e, just blank)
  3. Key press [Tab] [Tab] to focus message body. And key press a b c
> Do you use Firefox? if so, please paste this URL into the address bar. Are you available to reproduce it with this simple text box?
> 
> `data:text/html,<div contenteditable>editable text goes here</div>`

Not reproduce. It works as expected.

> Alternatively, try this:
> 
> `data:text/html,editable text goes here<script>document.designMode = "on";</script>`

Not reproduce. It works as expected.

Set release status flags based on info from the regressing bug 1957314

Hello, as with Alice, yes, I can reproduce it simply and repeatably. The two firefox examples work as expected. -KAM

Flags: needinfo?(kevin.mcgrail-mozillabugzilla)

I did some debugging with Thunderbird Daily. What's odd is that the UIA caret rectangle (which is what Text Cursor Indicator uses) changes as expected whenever the cursor moves. Text selection change events are also fired as expected whenever the caret moves. I can't test with Text Cursor Indicator myself, since I'm totally blind and it is entirely visual, so I'll have to wait until I can get some help with that.

In the meantime, can you reproduce it in Firefox if you do the following?

  1. Go to about:mozilla in the address bar.
  2. Open the Web Console by pressing control+shift+k.
  3. Paste the following command and press enter:
    document.body.innerHTML = ""; document.designMode = "on"
  4. Press f12 to close Developer Tools.
  5. Type into the (now empty) document.
Whiteboard: [uiaFastFollow]

James, the text cursor indicator works as expected in Thunderbird in the designMode test. -KAM

I still haven't gotten any further with this. :(

If you alt+tab out and back again, does that change anything? If you move the cursor using the left arrow key so that it's not at the end of the line, does that make any difference?

I checked with Daily149.0a1, It works as expected. (Although when opening the Composer window, even though the recipient field has focus, the text cursor indicator appears in the message body. This may be another new bug)

Fixed window:
https://hg-edge.mozilla.org/comm-central/pushloghtml?fromchange=4da11ed90536af2ce18a45e7cb384cdfc226cec7&tochange=33cc70d93d79646bb43967890efc25bbee8f4fd5
https://hg-edge.mozilla.org/mozilla-central/pushloghtml?fromchange=304947ca16aad74c19866a59fbe75230129ca192&tochange=0ea2a2b8832c7e69e6bd92944a67b0f03aee567c

Was it fixed in bug 2006816? And bug 2006816 causes the above new bug?

I lived with the bug for about a month before reporting it. I never saw any time it worked correctly using keyboard, mouse, alt+tab, etc. until I changed accessibility.uia.enable to 0 (from 2). -KAM

(In reply to Alice0775 White from comment #12)

Was it fixed in bug 2006816?

It's possible.

And bug 2006816 causes the above new bug?

That's less clear. Do you get the same regression window for the new bug?

Thanks for all of your help.

(In reply to James Teh [:Jamie] from comment #14)

(In reply to Alice0775 White from comment #12)

That's less clear. Do you get the same regression window for the new bug?

Thanks for all of your help.

Yes, The new issue started happening in the same regression window.

(In reply to Alice0775 White from comment #15)

Yes, The new issue started happening in the same regression window.

Okay. Bug 2006816 is the only change I can see in that regression window that should impact this, so I guess the new issue was indeed introduced by that.

Although when opening the Composer window, even though the recipient field has focus, the text cursor indicator appears in the message body.

Questions:

  1. Does this only occur the first time you open the composer or every time? That is, if you open the composer, close the composer and open the composer again, does the Text Cursor Indicator still appear in the wrong field?
  2. Does the Text Cursor Indicator correct its position as soon as you start typing into the recipient field?
  3. If you open the composer and tab to the Subject field, is the Text Cursor Indicator's position correct?
  4. If you then shift+tab back to the recipient field, is the Text Cursor Indicator's position correct?

Thanks.

Flags: needinfo?(alice0775)

(In reply to James Teh [:Jamie] from comment #16)

Questions:

  1. Does this only occur the first time you open the composer or every time? That is, if you open the composer, close the composer and open the composer again, does the Text Cursor Indicator still appear in the wrong field?

The issue reproduces every time the compose window is opened.
Yes, the Text Cursor Indicator appears in the wrong field.

  1. Does the Text Cursor Indicator correct its position as soon as you start typing into the recipient field?

Yes, the Text Cursor Indicator appears in the recipient field. And it works correctly for subsequent typing.

  1. If you open the composer and tab to the Subject field, is the Text Cursor Indicator's position correct?

Yes, the Text Cursor Indicator appears in the Subject field. And it works correctly for subsequent typing.

  1. If you then shift+tab back to the recipient field, is the Text Cursor Indicator's position correct?

Yes, the Text Cursor Indicatorr's position correct.

Flags: needinfo?(alice0775)
Depends on: 2006816
Depends on: 2015380

Now that bug 2015380 has landed, are all the issues identified in this bug fixed in Thunderbird Daily?

The two bugs covered here - bug 2006816 and bug 2015380 - are fixed, so I'm closing this. Please reopen if the problem persists.

Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → WORKSFORME

Thanks Jamie, could you let me know what version of Thunderbird they are resolved in and I can confirm they work, please?

These fixes will be in Thunderbird 149, which isn't officially released yet. If you are willing, you could try a beta or daily build. However, I totally understand if you don't want to do that, in which case I would wait a few weeks and test Thunderbird 149 when it is released.

(In reply to James Teh [:Jamie] from comment #21)

These fixes will be in Thunderbird 149, which isn't officially released yet. If you are willing, you could try a beta or daily build. However, I totally understand if you don't want to do that, in which case I would wait a few weeks and test Thunderbird 149 when it is released.

I'm game for a beta. Can you point me to a good W11 x64 build for testing? -KAM

You need to log in before you can comment on or make changes to this bug.