Bug 119281 - Ctrl+i does not italicise the word
Summary: Ctrl+i does not italicise the word
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.2.0.0.alpha0+
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-15 06:25 UTC by Elmar
Modified: 2018-09-23 15:54 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
everything change ok (131.28 KB, image/jpeg)
2018-08-16 07:35 UTC, BogdanB
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Elmar 2018-08-15 06:25:06 UTC
Description:
This is also true in v6.0.6.2
If place cursor in a word (or select the whole word or multiple words) and do Ctrl+B, Ctrl+U etc. then the action is executed, but not for Ctrl+I. Need to use the tool bar to achieve this.

Steps to Reproduce:
1. place cursor in a word (or select a range)
2. Ctrl+i
3. nothing changes
do same with ctrl+b, etc, and the the text is affected as expected

Actual Results:
nothing

Expected Results:
selection or identified word should display as italics.


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
Version: 6.2.0.0.alpha0+
Build ID: a94a481c9f5088e6957220a7e09b64fc3f15aaf1
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk2; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2018-08-09_22:42:59
Locale: en-ZA (en_ZA.UTF-8); Calc: threaded

But is also true in v6.0.6.2
(I think this is a regression -  I do this all the time and would have used it in v5, but cannot say for certain)
Comment 1 raal 2018-08-15 08:59:56 UTC
no repro with Version: 6.2.0.0.alpha0+
Build ID: 1da9b165b9c47f52db97fe70fe3e83626e580cdd
CPU threads: 4; OS: Windows 6.1; UI render: default;
Comment 2 Xisco Faulí 2018-08-15 10:04:40 UTC
if you type a word and then you use space, it should work,

Version: 6.2.0.0.alpha0+
Build ID: 18e20676024baecaf5719139f80f053f5f1e784a
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: threaded

however, if you doesn't add a space, it doesn't italize the word, because it doesn't know where it starts and ends...
Comment 3 Timur 2018-08-15 10:11:31 UTC
Also no repro for me. I hope Xisco's comment clarified. 

If you're reporting broken some basic and frequent function like this, make sure you understand what's wrong. 
I mean do not feel free to first report and oblige QA with not reproducing, without searching other bugs and personal test with other computers and O versions. 
I see that you have a number of reports, some useful, but majority reported a bit too soon.
Comment 4 BogdanB 2018-08-16 07:35:34 UTC
Created attachment 144228 [details]
everything change ok
Comment 5 BogdanB 2018-08-16 07:36:44 UTC
I created 3 sentences, click on a word and Ctr+B. It became bold. The same with Ctr+U and became underline. And the same with Ctr+I and became italic.

No problem on my version:
Versiune: 6.1.0.3
Identificator construire: efb621ed25068d70781dc026f7e9c5187a4decd1
Fire CPU: 4; OS: Linux 4.15; Redare UI: GL; VCL: gtk2; 
Setări regionale: ro-RO (ro_RO.UTF-8); Calc: group threaded
Comment 6 Timur 2018-08-29 15:21:32 UTC
Since no response from reporter, according to Comment 2, I'll close. 
Elmar, if you consider this a bug please explain what is requested.
Comment 7 Elmar 2018-08-30 16:44:02 UTC
When I save the custom shortcuts I find the following:
 <accel:item accel:code="KEY_I" xlink:href=".uno:Italic" accel:mod1="true"/>
 <accel:item accel:code="KEY_I" xlink:href=".uno:SelectTextMode" accel:shift="true" accel:mod1="true"/>

I do not know how I could have caused this.

But it does seem to be a conflict?
Comment 8 Buovjaga 2018-09-23 15:54:35 UTC
(In reply to Elmar from comment #7)
> When I save the custom shortcuts I find the following:
>  <accel:item accel:code="KEY_I" xlink:href=".uno:Italic" accel:mod1="true"/>
>  <accel:item accel:code="KEY_I" xlink:href=".uno:SelectTextMode"
> accel:shift="true" accel:mod1="true"/>
> 
> I do not know how I could have caused this.
> 
> But it does seem to be a conflict?

Ok, but if you find a way to cause it, you could open a new report.