Bug 137201 - EDITING: Unable to type to manually change font family when text is partially or fully selected (GTK3)
Summary: EDITING: Unable to type to manually change font family when text is partially...
Status: VERIFIED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
7.0.1.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Caolán McNamara
URL:
Whiteboard: target:7.1.0 target:7.0.3
Keywords:
: 134037 (view as bug list)
Depends on:
Blocks: GTK3
  Show dependency treegraph
 
Reported: 2020-10-02 06:11 UTC by Reinhart Previano
Modified: 2020-10-26 17:46 UTC (History)
2 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 Reinhart Previano 2020-10-02 06:11:15 UTC
Description:
In previous versions of LibreOffice (upgraded from LO 6.5), it was possible to manually change the font name of a selected (not entire) text by trigerring Ctrl+A on the font selection dropdown. The latest update in Impress broke the functionality.

Steps to Reproduce:
1. Create a new Impress presentation
2. Type some text on text fields (e.g. Headings and Subheadings)
3. Select part or all of the text
4. Select the font name on the Sidebar (under "Character")
5. Try Select All (Ctrl+A) on the font name field

Actual Results:
The font name is not selected, triggering Ctrl+A now highlights the entire text instead. Manually renaming the font name is now more difficult.

Expected Results:
In previous versions of LibreOffice (upgraded from LO 6.5), the name of the selected font should be selected.


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Full Installation Information:

Version: 7.0.1.2
Build ID: 00(Build:2)
CPU threads: 12; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Ubuntu package version: 1:7.0.1_rc2-0ubuntu0.20.04.1
Calc: threaded
Comment 1 Buovjaga 2020-10-17 14:24:51 UTC

*** This bug has been marked as a duplicate of bug 134939 ***
Comment 2 Buovjaga 2020-10-17 16:34:42 UTC
Bug 134939 was fixed, but this issue still remains, so undoing my closing as duplicate.
Comment 3 Caolán McNamara 2020-10-17 18:43:07 UTC
its very similar, another spot with the same basic problem
Comment 4 Commit Notification 2020-10-17 20:12:14 UTC
Caolán McNamara committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/d89a2b67ee74998b12ca7d23fb2b1717301a3f95

Resolves: tdf#137201 don't update IM if focus is in another widget

It will be available in 7.1.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 5 Caolán McNamara 2020-10-17 20:12:42 UTC
fixed in master, backport to 7-0 in gerrit
Comment 6 Buovjaga 2020-10-18 14:16:04 UTC
Verified, thanks

Arch Linux 64-bit
Version: 7.1.0.0.alpha0+
Build ID: ccdb78773ac6c9d19140e8084f37cc2c7f06240e
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 18 October 2020
Comment 7 Commit Notification 2020-10-19 09:22:06 UTC
Caolán McNamara committed a patch related to this issue.
It has been pushed to "libreoffice-7-0":

https://git.libreoffice.org/core/commit/d76e9fc4edcdf9a44cb2ed9542261064a8a76dde

Resolves: tdf#137201 and tdf#134939 don't update IM if focus is in another widget

It will be available in 7.0.3.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.
Comment 8 Buovjaga 2020-10-26 17:46:08 UTC
*** Bug 134037 has been marked as a duplicate of this bug. ***