Bold/Italic/Underline problem in composition window
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
People
(Reporter: davofanmail, Unassigned)
Details
Attachments
(1 file)
19.55 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/119.0
Steps to reproduce:
Open message composition window.
Type a line of text.
Hit return (force a new "paragraph")
Type some text. Then, Ctrl-I or push the I button to make the next word Italic.
Continue typing.
Ctrl-I to return to normal text.
Continue typing
Actual results:
On the FIRST line of text, the composition window handles the font emphasis transitions perfectly (italic, bold, underline)
On subsequent lines, it does not:
- the Italic Ior bold, or underline) button IS properly selected
- but the cursor jumps back to the start of the line, where the emphasis is not on
- subsequent typing is from the first character of the line with no emphasis, rather than having the emphasis on at the end where your cursor was originally.
Note that if you have no text on a subsequent line and turn on any of the emphasis modes from the very first character, everything behaves properly for that line.
This behavior just started at v115.0 on windows 10. Appears to be fully repeatable, at least on my system.
Expected results:
The text should be in tact, with only the identified words italicized (or bolded or underlined). See attached screen capture
cursor jumps back to the start of the line > bug 1852849.
Windows 10 OS
Testing in beta 120.0b7
Start typing several words and then use 'Ctrl+I' and continue typing, Text is now italic
Use 'Ctrl+B' and continue typing text is now italic and bold,
Use 'Ctrl+U' and text is now italic, bold and underlined.
Use 'Shift+Ctrl+Y' and type
All formatting is back to normal text
Press Enter to go to new line
Repeat the above, but this time keep typing and use 'Ctrl+U' and underline is switched off
kepp typing and use 'Ctrl+B' and keep typing
finally use 'Ctrl+I' and keep typing - I'm back to normal text.
All worked as expected.
I'm not able to reproduce this bug in beta 120.0b7
Right, because it was fixed in bug 1852849 in Mozilla platform 120.
Updated•10 months ago
|
Description
•