[Bug 159554] Red vs. Orange background - BackgroundParaOverDrawings True vs. False

2024-02-06 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159554

Mike Kaganski  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||1974,
   ||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||2158

--- Comment #3 from Mike Kaganski  ---
(In reply to Tex2002ans from comment #2)
> - On Copy/Paste to new document, trying to carry over these compatibility
> flags becomes a nightmare (and has caused many large regressions in the
> past).

Right. Carrying compat flags was accidentally happening in the past, and became
visible after commit a7d9837a8aa6d1233f4c21e4db5d32428a3ffc58, and caused bugs
151974, 151728, 152158 (see bug 151728 comment 4). It was fixed by commit
2d0a87f97e2c9ac50cd6ce329ca8256daf94ead4.

Carrying flags would mean that, while the copied data would look as it was in
the source, the *already existing text* in the target document could suddenly
change its formatting. It is the sad outcome of having compatibility flags at
all; and we indeed try hard to allow working with external formats, with their
differences in behavior.

The problem here is invisibility of the compatibility flag(s) to user. Making
flags accessible is of course important, but even when we add that flag to the
Options->Writer->Compatibility, will anyone really find out that some specific
(of tens, potentially hundreds) flag there is responsible for the difference?

MS Word adds a "[Compatibility Mode]" decoration to the document's title bar.
Would it help? Maybe. Yet, given the huge amount of compat flags, it is easily
possible, that both of your documents are is "compatibility modes" (i.e., some
of the compatibility flags are in non-default state), but in *different*
compatibility modes...

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

[Bug 159554] Red vs. Orange background - BackgroundParaOverDrawings True vs. False

2024-02-06 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159554

Tex2002ans  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 CC||mikekagan...@hotmail.com,
   ||Tex2002ans+LibreOffice@gmai
   ||l.com
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=12
   ||6513
 Ever confirmed|0   |1

--- Comment #2 from Tex2002ans  ---
I can confirm this on:

Version: 24.2.0.3 (X86_64) / LibreOffice Community
Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1
CPU threads: 8; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

- - -

The root cause was a compatibility setting called:

- BackgroundParaOverDrawings

The "Right" file had:

- BackgroundParaOverDrawings = true

The "Wrong" file had:

- BackgroundParaOverDrawings = false

where:

- Right = Red background
- Wrong = Orange/Peach background (+ slightly different formatting)

- - -

Note #1: Me and Mike Kaganski live-debugged this one together a few days ago,
so I am CCing him.

- - -

Note #2: Adding "Bug #126513" to See Also, based on Kaganski's detective-work.
>From what he was telling me, I believe it was:

- A setting that is possible to READ, but currently no way for LO to actually
tweak/change/adjust after.
- On Copy/Paste to new document, trying to carry over these compatibility flags
becomes a nightmare (and has caused many large regressions in the past).

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

[Bug 159554] Red vs. Orange background - BackgroundParaOverDrawings True vs. False

2024-02-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=159554

heath  changed:

   What|Removed |Added

 CC||heath...@gmail.com

--- Comment #1 from heath  ---
Created attachment 192386
  --> https://bugs.documentfoundation.org/attachment.cgi?id=192386=edit
right and wrong files

the 'right' file is how I want it to look (created on a previous version of
Writer). The wrong file is how it looks in a newly created Writer document.

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