Bug 148618 - Font size in fields is incorrect depending on the zoom level
Summary: Font size in fields is incorrect depending on the zoom level
Status: RESOLVED DUPLICATE of bug 148400
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.4.0.0 alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks:
 
Reported: 2022-04-15 20:29 UTC by Xisco Faulí
Modified: 2022-04-20 14:31 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

Attachments
sample file (11.62 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2022-04-15 20:29 UTC, Xisco Faulí 		Details
wrong vs right (73.36 KB, image/png)
2022-04-15 20:30 UTC, Xisco Faulí 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Xisco Faulí 2022-04-15 20:29:40 UTC 
Created attachment 179597 [details]
sample file

Steps to reproduce:
1. Open attached document
2. Zoom in and out

-> Font size is incorrect

Reproduced in

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: ab8d141967111ca81f4607db3618bb09214e42db
CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3
Locale: es-ES (es_ES.UTF-8); UI: en-US
Calc: threaded

and GEN
Comment 1 Xisco Faulí 2022-04-15 20:30:57 UTC 
Created attachment 179598 [details]
wrong vs right
Comment 2 Xisco Faulí 2022-04-15 20:31:49 UTC 
Regression introduced by:

author	Luboš Luňák <l.lunak@collabora.com>	2022-04-07 12:06:27 +0200
committer	Luboš Luňák <l.lunak@collabora.com>	2022-04-08 21:29:19 +0200
commit 3e5863605881c6de6ad130fe06883c176ca1c69f (patch)
tree 9e7863107a162eba8952710af00c281b91a12633
parent 53fe4a26c7c4691fcf9d07d022adfd45247d176b (diff)
use just one shared global SalLayoutGlyphsCache

Bisected with: bibisect-linux64-7.4

Adding Cc: to Luboš Luňák
Comment 3 Luboš Luňák 2022-04-20 14:31:01 UTC 

*** This bug has been marked as a duplicate of bug 148400 ***