Bug 135115 - Styles Inspector: show Paragraph direct formatting
Summary: Styles Inspector: show Paragraph direct formatting
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Hardware: All All
: medium normal
Assignee: Aron Budea
Whiteboard: target:7.1.0
Depends on:
Blocks: Styles_Inspector
  Show dependency treegraph
Reported: 2020-07-24 20:32 UTC by Mike Kaganski
Modified: 2020-09-28 20:28 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

A simple FODT with direct formatting on character and paragraph levels (28.21 KB, application/vnd.oasis.opendocument.text)
2020-07-24 20:32 UTC, Mike Kaganski

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Kaganski 2020-07-24 20:32:06 UTC
Created attachment 163492 [details]
A simple FODT with direct formatting on character and paragraph levels

In attached document, the range from last part of first paragraph to first part of third paragraph is manually set *bold*. additionally, second word of second paragraph is manually set not bold.

Using Styles Inspector, putting cursor to first (normal) part of first paragraph shows exactly the same data as putting the cursor to bold parts of the second paragraph. That is because the direct properties that are set on paragraph level are not shown.

They must be shown after paragraph styles, before character styles. To get them, we need to obtain a reference to the paragraph (also a XTextRange) that is parent to current XTextRange, and query its direct properties the same way as we do for XTextRange.

To obtain the paragraph reference, query css::container::XEnumerationAccess from the xRange; then get enumeration, and use its first element.
Comment 1 Commit Notification 2020-09-19 21:00:37 UTC
Aron Budea committed a patch related to this issue.
It has been pushed to "master":


tdf#135115: show paragraph direct formatting in Styles Inspector

It will be available in 7.1.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:

Affected users are encouraged to test the fix and report feedback.