Bug 170167 - Loss of paragraph inset tab when typing a return at the end of a paragraph in Writer
Summary: Loss of paragraph inset tab when typing a return at the end of a paragraph in...
Status: RESOLVED DUPLICATE of bug 170146
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
25.8.4.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-12-29 21:53 UTC by David Palmer
Modified: 2025-12-29 22:04 UTC (History)
1 user (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 David Palmer 2025-12-29 21:53:25 UTC
Description:
After I installed 25.8.4.2, in Writer, whenever I use a tab to create an inset at the beginning of a paragraph, when I perform an enter or return at the end of the paragraph, the inset at the beginning of the paragraph is immediately removed.  I could find no format setting that would prevent the problem so I reinstalled version 25.8.2 (which upgraded to 25.8.3 automatically).  Version 25.8.3 does not display the described problem.  

Steps to Reproduce:
1.Tab at the beginning of a paragraph to create an inset first line.
2.Type paragraph as desired. May including multiple sentences.  
3.At the completion of the paragraph, type a return or enter key to start the next paragraph. 

Actual Results:
The inset at the beginning of the paragraph is removed.  The paragraph begins at the left margin.  

Expected Results:
A new paragraph is begun at the left margin and the previous paragraph is left unchanged.


Reproducible: Always


User Profile Reset: No

Additional Info:
Earlier paragraphs are not impacted. If I return to the beginning of the impacted  paragraph, I can reinsert a tab to create the desired inset which remains as long as I do not insert a return anywhere in that particular paragraph.
Comment 1 m_a_riosv 2025-12-29 22:04:35 UTC

*** This bug has been marked as a duplicate of bug 170146 ***