Customer reported that in some cases message date is incorrect when using print function, as it displays date of the first message in the thread instead of the selected message date.
I was able to reproduce this issue:
- open thread with multiple encrypted messages
- click
expand all button:
- click
print on the second message in the thread
- print page will use date of the first message, instead of the second
This bug isn't reproducible when first message isn't expanded - print page correctly uses date of the selected message in this case.
So seems like this bug in parsing message date happens when the first thread message is visible.
Customer reported that in some cases message date is incorrect when using print function, as it displays date of the first message in the thread instead of the selected message date.
I was able to reproduce this issue:
expand allbutton:printon the second message in the threadThis bug isn't reproducible when first message isn't expanded - print page correctly uses date of the selected message in this case.
So seems like this bug in parsing message date happens when the first thread message is visible.