Bug 129332 - Writer: Autotext adds a line feed, and inserts text with a fixed font size
Summary: Writer: Autotext adds a line feed, and inserts text with a fixed font size
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.1 all versions
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-11 17:41 UTC by Tim Slater
Modified: 2021-02-09 12:47 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Slater 2019-12-11 17:41:28 UTC
Description:
Editing: When I insert an Autotext item in a document with F3, it enters the text with a fixed font size (instead of the current setting in the text), and adds a return/line feed.

Steps to Reproduce:
1.Enter an abbreviation from the Autotext list
2. Type F3 after the abbreviaton.
3.

Actual Results:
As stated above.

Expected Results:
Enter the text using the current font settings, and followed by a space.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Comment 1 V Stuart Foote 2019-12-12 01:25:33 UTC
Thanks for filing, but can not confirm on Windows 10 with current 6.3.3.2 release. The Autotext entry made into a paragraph where the nemonic is entered will pick up the direct formatting or the style applied to the paragraph.

As the 6.1 build is well past EOL, are you able to update and test with a current release?  At the least, please either reset your profile, or use the 'Restart in Safe Mode..." from the Help menu to get a clean user profile and retest.
Comment 2 QA Administrators 2020-06-10 03:48:42 UTC Comment hidden (obsolete)
Comment 3 Tim Slater 2020-06-10 17:04:56 UTC
After updating to the newest version from the Still Branch, 6.3.6.2, the problem seems to have been solved in that version.
Comment 4 Xisco Faulí 2021-02-09 12:47:01 UTC
Thanks for retesting the issue with the latest version.
Setting to RESOLVED WORKSFORME since the commit fixing this issue hasn't been
identified.