https://bugs.documentfoundation.org/show_bug.cgi?id=156748

Colin <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|1                           |0
             Status|NEEDINFO                    |UNCONFIRMED

--- Comment #3 from Colin <[email protected]> ---
(In reply to Stéphane Guillou (stragu) from comment #2)
> Created attachment 189276 [details]
> ODS of test result (could not reproduce)
> 
> 
> Can you please provide an example file and more precise steps to reproduce
> the issue?

Attached is a small .ods which was created before outlines were changed to
obviate the clash with Excel.

All outlines were originally created at the thinnest setting and the
conditional formatting also "standardised" with the then-current thinnest
outline.

Recent changes to the outlines have obviously defaulted to current Excel
compliance.

Embedded within the conditional formatting (and elsewhere in the sheet) are the
original "fine lines". These fine lines never "clashed" with the underlying
outlines because they were the same and so only the "Fill colour" was
conditioned.

To demonstrate

     1) EDIT the date in B1 to 22/8/23
     2) CYCLE between the undo and redo actions on the toolbar

This demonstrates the clash between the new Excel compliance and probably
millions of LO files when a user unknowingly amends either a conditional format
or the simple applied cell format.

There is a "sort of" workaround but only when the impact is exclusively on the
outside edge of an array AND if the user wishes to create lots of "micro
columns" in which to play.

     1) Select E1:E17
     2) Place an outside or left side border of the default thickness
     3) Flip-flop between the two identified dates as per test 1 above.

The dates are specifically Tuesdays and Fridays (Formulae in Column G) and the
"trigger" is column H with Friday = 1 and anything that isn't Friday being a 2.

Normally, only the "candystripe" columns are visible and what is presented is
an optimisation of the worst impacted portion of the "Dashboard" 

It is not user centric to be required to re-define all existing conditional
formats to comply with the Excel precepts

Yes I know the sample is mickey mouse but it's part of a seven sheet file
developed over 8 years with inter-sheet links and extensive use of conditional
fills - quite a few within the domain of outlined and highlighted arrays.

Note: Columns G, I & J are also subject to the same conditional formatting but
their outlines have not been affected by the subsequent placement of the "new"
standard outline weights so there is no visible interference.

It is also possible to copy a pre Excel format from another LO sheet and retain
the original embedded criteria.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to