Bug 139642 - Deactivating/activating (numbered) list and undoing changes font of certain entries
Summary: Deactivating/activating (numbered) list and undoing changes font of certain e...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.3.0.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks: Bullet-Number-Outline-Lists Undo-Redo
  Show dependency treegraph
 
Reported: 2021-01-15 13:06 UTC by Telesto
Modified: 2023-12-01 11:09 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file (6.72 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2021-01-15 13:07 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2021-01-15 13:06:55 UTC
Description:
Disabling/enabling (numbered) list and undo changes font of certain entry's

Steps to Reproduce:
1. Open the attached file
2. CTRL+A
3. Click bulleted list button -> Toggles of
4. Press it again -> Toggles on
5. Undo

Actual Results:
Font appears bigger compared to initially (however font settings appear to be the same in the dialog
Position for numbering has different font

Expected Results:
Same font.. and no mixing


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.2.0.0.alpha0+ (x64)
Build ID: f2171af6ce3516598d9f8bac8294025a21a5b1a2
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL
Comment 1 Telesto 2021-01-15 13:07:11 UTC
Created attachment 168910 [details]
Example file
Comment 2 Telesto 2021-01-15 13:08:41 UTC
Also in
4.4.7.2 -> already on file open

fine in
Versie: 4.2.0.4 
Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba71
Comment 3 Telesto 2021-01-15 13:09:58 UTC
Also in
Version: 4.3.7.2
Build ID: 8a35821d8636a03b8bf4e15b48f59794652c68ba
Comment 4 Dieter 2021-05-19 13:35:16 UTC
I can't confirm it with

Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 1675a68526c43c6c6e4dc850ee911f0c1de75c88
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL

Font is DejaVu Sans 8pt after step 3 and after step 5
Comment 5 Buovjaga 2021-09-11 18:51:14 UTC
Repro. Step 5 should be: undo everything or undo twice.

Btw. instead of looking at 4.x where the font already appeared bigger, I guess we should rather be looking at some change where the toggle & undo steps apply.

Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: e6a8d312d3d7e5d81c56d5ccc0508116dd283f1f
CPU threads: 8; OS: Linux 5.14; UI render: default; VCL: kf5 (cairo+wayland)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Comment 6 Henrik Palomäki 2021-09-13 09:19:11 UTC
I done a bibisect using the win64-7.0 repository for "toggle - undo" bug and found: 

https://git.libreoffice.org/core/commit/6287845eab339a8eb3c660d648d012e9f1dcce30

Adding Cc: to László Németh

I searched the commit and found that this was a fix for the bug 127606. It may have happened that it caused this regression.

It seems that the other "already bigger font on file open" issue disappeared at least starting from the version 6.4.0.1. So, I think it can be considered as a wfm.
Comment 7 Stéphane Guillou (stragu) 2023-06-26 15:22:51 UTC
still reproduced in:

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 9fc0b2b9b96d87eb642a3b29e9dcb5d6273265eb
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Using steps:

1. Open the attached file
2. CTRL+A
3. Click bulleted list button -> Toggles of
4. Press it again -> Toggles on
5. Undo everything
Comment 8 Stéphane Guillou (stragu) 2023-12-01 11:09:04 UTC
(In reply to Henrik Palomäki from comment #6)
> I done a bibisect using the win64-7.0 repository for "toggle - undo" bug and
> found: 
> https://git.libreoffice.org/core/commit/
> 6287845eab339a8eb3c660d648d012e9f1dcce30
I checked the bisect, it's true that there was a change at this commit, which makes it look like it was momentarily fixed before then, but:
linux-64-6.4 master: bad
linux-64-7.0 oldest: good 6287845eab339a8eb3c660d648d012e9f1dcce30: bad

...so I can't find out more.

László, any thoughts?