Bug 1777454 Comment 58 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
I have smoketested [TB 102.0.3 candidate build](https://archive.mozilla.org/pub/thunderbird/candidates/102.0.3-candidates/build1/) today (not yet released), and using my steps from Comment 55, I have not been able to reproduce the inbox display corruption.

It would be great if users affected by this bug or bug 1777738 respectively could try the following:

1. On [TB 102.0.2 (affected)](https://ftp.mozilla.org/pub/thunderbird/releases/102.0.2/), execute STR of comment 55, which should cause message display corruption on the last received message (at least).
2. On [TB 102.0.3 candidate build](https://archive.mozilla.org/pub/thunderbird/candidates/102.0.3-candidates/build1/), execute STR of comment 55 again (try to do it in exactly the same way) - which should no longer cause message display corruption.
3. Let us know SUCCESS if you're seeing the problem in 102.0.2, but no longer seeing it in 102.0.3.
  Otherwise report FAIL if you cannot reproduce with comment 55 in 102.0.2 OR if you can still reproduce in 102.0.3, and say where/in which way it failed.
Revision 1 by
on 
I have smoketested [TB 102.0.3 candidate build](https://archive.mozilla.org/pub/thunderbird/candidates/102.0.3-candidates/build1/) today (not yet released), and using my steps from Comment 55, I have not been able to reproduce the inbox display corruption.

It would be great if users affected by this bug or bug 1777738 respectively could try the following:

1. On [TB 102.0.2 (affected)](https://ftp.mozilla.org/pub/thunderbird/releases/102.0.2/), execute STR of comment 55, which should cause message display corruption on the last received message (at least).
2. On [TB 102.0.3 candidate build](https://archive.mozilla.org/pub/thunderbird/candidates/102.0.3-candidates/build1/), execute STR of comment 55 again (try to do it in exactly the same way) - which should no longer cause message display corruption.
3. Let us know SUCCESS if you're seeing the problem in 102.0.2, but no longer seeing it in 102.0.3.
  Otherwise report FAIL if you cannot reproduce with comment 55 in 102.0.2 OR if you can still reproduce in 102.0.3, and say where/in which way it failed. Keep your comment as short as possible.
Revision 2 by
on 
I have smoketested [TB 102.0.3 candidate build](https://archive.mozilla.org/pub/thunderbird/candidates/102.0.3-candidates/build1/) today (not yet released), and using my steps from Comment 55, I have not been able to reproduce the inbox display corruption.

It would be great if users affected by this bug 1777454 or bug 1777738 respectively could try the following:

1. On [TB 102.0.2 (affected)](https://ftp.mozilla.org/pub/thunderbird/releases/102.0.2/), execute STR of comment 55, which should cause message display corruption on the last received message (at least).
2. On [TB 102.0.3 candidate build](https://archive.mozilla.org/pub/thunderbird/candidates/102.0.3-candidates/build1/), execute STR of comment 55 again (try to do it in exactly the same way) - which should no longer cause message display corruption.
3. Let us know SUCCESS if you're seeing the problem in 102.0.2, but no longer seeing it in 102.0.3.
  Otherwise report FAIL if you cannot reproduce with comment 55 in 102.0.2 OR if you can still reproduce in 102.0.3, and say where/in which way it failed. Keep your comment as short as possible.

Back to Bug 1777454 Comment 58