Bug 124897 - Conditional format is changing format templates
Summary: Conditional format is changing format templates
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.1.5.2 release
Hardware: All Mac OS X (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Conditional-Formatting
  Show dependency treegraph
 
Reported: 2019-04-23 08:12 UTC by Joachim Wetzig
Modified: 2019-11-22 03:41 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
Screenshot of cell templates (331.90 KB, image/png)
2019-04-23 08:12 UTC, Joachim Wetzig
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joachim Wetzig 2019-04-23 08:12:15 UTC
Created attachment 150932 [details]
Screenshot of cell templates

Greetings,

running LO on Mac:
Version: 6.1.5.2
Build-ID: 90f8dcf33c87b3705e78202e3df5142b201bd805
CPU-Threads: 8; BS: Mac OS X 10.13.6; UI-Render: Standard; 
Gebietsschema: de-DE (de_DE.UTF-8); Calc: group threaded

Setting up conditional format (CF) to ONLY format SOME property of a cell's format by adding a new format template, setting e. g. only background every other line (yup: still love that old line printer striped output style...) or setting only font color.

When using the CF and copying it to other cells it bloats by adding other properties from cells. I have not been able to identify WHEN this happens.

Example screenshots attached as a) new template setting only RGB [Bildschirmfoto 2019-04-23 um 09.50.38.png] and b) a template after repeated use [Bildschirmfoto 2019-04-23 um 09.50.56.png].

It would be nice, if 
1) - (preferred) one could control this "sucking up" of properties by explicitly allowing or denying it or 
2) - (less desirable) one could remove unwanted properties from the template after the fact 
(1) and 2) would make templates more useful, too) or
3) - (alternatively, but less flexible) it would not happen.

Cheers

Jo
Comment 1 Alex Thurgood 2019-04-23 09:21:50 UTC
@Joachim:

A detailed set of instructions with sample files so that we could try and observe the behaviour ourselves would be most useful, otherwise it is going to be hard to confirm, especially seeing as you have admitted that you don't know exactly when this occurs.

I seem to recall that cell text attributes have been "picked up" for quite a while now, and it is just that in your particular use case has irked you enough to raise a flag ;-)

When you write the following :

"When using the CF and copying it to other cells it bloats by adding other properties from cells. I have not been able to identify WHEN this happens."


What exactly do you mean ? Which other properties in particular ? Or, are only some properties picked up, seemingly at random ?

Setting NEEDINFO
Comment 2 Alex Thurgood 2019-04-23 09:24:08 UTC
One way to try and pin down the changes would be to carry out a comparison of the XML produced in the ODS file before and after application of the template.
Comment 3 QA Administrators 2019-10-22 02:32:33 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2019-11-22 03:41:27 UTC
Dear Joachim Wetzig,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp