Bug 132769 - Different Font name/font size overlap when moving the cursor around paragraphs written in different fonts/sizes
Summary: Different Font name/font size overlap when moving the cursor around paragraph...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
6.4.3.2 release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Notebookbar-Tabbed
  Show dependency treegraph
 
Reported: 2020-05-06 13:11 UTC by fogexi4163
Modified: 2022-06-23 03:49 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fogexi4163 2020-05-06 13:11:31 UTC
Description:
I tried my best summing it up in the title.

I will try to explain it better here.

If I have a paragraph in which half is in Arial and another is in Times New Roman, and i move the cursor using the keyboard from the beggining to the end of it, the name of the font in the Ribbon will overlap (so in this case Arial+TNR). The same is true for different font sizes. I attached two pictures to explain what I mean. 

https://imgur.com/a/iJVWYdX

I can also reproduce the bug by first selecting a word written in Arial, deselecting it, and then selecting one in TNR. Same goes for different font sizes.

It happens regardless of font or size.



Steps to Reproduce:
1. Have a text with two font names (eg Arial and times new roman)
2. Select the word in arial
3. Deselect it
4. Select the one in TNR
5. Now font name will overlap like in the picture.

This is true for font size as well

Actual Results:
Font name overlap

Expected Results:
No overlapping


Reproducible: Always


User Profile Reset: No



Additional Info:
Versiune: 6.4.3.2
Identificator construire: 6.4.3.2-1.fc32
Fire CPU: 8; OS: Linux 5.6; Redare UI: implicit; VCL: gtk3; 
Setări regionale: ro-RO (ro_RO.UTF-8); UI-Language: ro-RO
Calc: threaded
Comment 1 Buovjaga 2020-08-31 16:29:29 UTC
No problem here

Arch Linux 64-bit
Version: 7.1.0.0.alpha0+
Build ID: d784e711c102f204552c3c816636da01b1085f61
CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: gtk3
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 29 August 2020
Comment 2 andreas_k 2020-09-01 20:54:19 UTC
can you upload the odt file with the "problem" paragraph.
Comment 3 Xisco Faulí 2021-11-23 10:53:48 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Comment 4 QA Administrators 2022-05-23 03:38:56 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2022-06-23 03:49:10 UTC
Dear fogexi4163,

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