Bug 136867 - Show stubs in Styles Inspector for complex properties not yet handled properly
Summary: Show stubs in Styles Inspector for complex properties not yet handled properly
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Style-Inspector
  Show dependency treegraph
 
Reported: 2020-09-18 05:47 UTC by Mike Kaganski
Modified: 2022-09-24 03:42 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 Mike Kaganski 2020-09-18 05:47:39 UTC
E.g. bug 136596 discusses missing language property. The problem is that any complex property (containing a struct) that is not handled explicitly (only border is ATM) is silently discarded in svx::sidebar::GetPropertyValues.

For such properties, we should still show at least a stub, like

> Some Property             <struct>

which would be informative both in the sense that user would see that it's present/defined at this level, and in the sense that it will be clear what is TODO yet (to process specially and display useful value).
Comment 1 Aron Budea 2020-09-23 23:33:02 UTC
This is fair, but also a bit tricky, because I see unhandled entries like this under Direct Formatting even with a completely empty document:
- List Auto Format,
- List Id,
- List Label String,
- Para Chapter Numbering Level,
- Text Paragraph.
Comment 2 QA Administrators 2022-09-24 03:42:03 UTC
Dear Mike Kaganski,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug