Bug 139079 - Clear direct formatting should NOT delete page breaks
Summary: Clear direct formatting should NOT delete page breaks
Status: RESOLVED DUPLICATE of bug 73483
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Hardware: All All
: medium enhancement
Assignee: Not Assigned
Keywords: needsUXEval
Depends on:
Reported: 2020-12-19 20:35 UTC by R. Green
Modified: 2020-12-20 14:31 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description R. Green 2020-12-19 20:35:04 UTC
Version: (x64)
Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: en-GB (en_GB); UI: en-GB
Calc: threaded

The most natural and fastest way to clear ad hoc formatting from a WRITER file SHOULD be to select ALL and apply "Clear direct formatting". But this cannot be done because the command (inexplicably) deletes page breaks as well.

(Even worse, the deletion of page breaks does not show up until the document is saved and reloaded: see Bug 73483.)

Imagine a book with many chapters, and it has become apparent that there is character formatting applied willy nilly throughout the document. The user wants to remove this leaving only the paragraph and character styles. To avoid losing page breaks, the user has to apply "Clear direct formatting", section by section, skipping the page breaks. A very time-consuming and tedious business.

IMV, the average user is likely to assume (wrongly) that "Clear direct formatting" only applies to text and should leave page breaks alone.

SUGGESTION: "Clear direct formatting" should NOT delete page breaks. Instead there should be another command, "Clear page breaks", to delete the page breaks separately.
Comment 1 Timur 2020-12-20 08:15:07 UTC
You commented there. No point in opening another big for this movie issue.

*** This bug has been marked as a duplicate of bug 73483 ***
Comment 2 Timur 2020-12-20 08:16:00 UTC
No point in opening another bug for this minor issue.