Bug 111311 - EDITING: Blue header line will disappear after inserting a special character
Summary: EDITING: Blue header line will disappear after inserting a special character
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.4.0.3 release
Hardware: All All
: medium trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisectRequest, regression
Depends on:
Blocks:
 
Reported: 2017-08-03 12:17 UTC by Telesto
Modified: 2019-05-15 09:33 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
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 Telesto 2017-08-03 12:17:10 UTC 
Description:
Blue header line will disappear after inserting a special character

Steps to Reproduce:
1. Open Writer
2. Insert the header
3. Press the Insert Character button
4. Select a character and apply -> the blue header line will disappear 

Actual Results:  
The blue header line will disappear

Expected Results:
Shouldn't happen


Reproducible: Always

User Profile Reset: No

Additional Info:
Repro with:
Version: 5.4.0.3
Build ID: 7556cbc6811c9d992f4064ab9287069087d7f62c
CPU threads: 4; OS: Windows 6.2; UI render: default; 
Locale: nl-NL (nl_NL); Calc: CL

No repro with:
Version: 6.0.0.0.alpha0+
Build ID: 9ca7bda2cc8b67c2d10fcb81cce8bfd4d8b79b09
CPU threads: 4; OS: Windows 6.19; UI render: default; 
TinderBox: Win-x86@39, Branch:master, Time: 2017-08-02_01:19:29
Locale: nl-NL (nl_NL); Calc: CL


User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Comment 1 Jacques Guilleron 2017-08-03 16:27:18 UTC 
Hi Telesto,

Reproduced with 
LO 5.4.0.3 (x64) Build ID: 92c2794a7c181ba4c1c5053618179937228ed1fb
Threads CPU : 2; OS : Windows 6.1; UI Render : par défaut; 
Locale : fr-FR (fr_FR); Calc: CL
but not with
LO 6.0.0.0.alpha0+ Build ID: 643da8ec4e721d33dfdf8d78bedd50a915f1188d
CPU threads: 2; OS: Windows 6.1; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2017-06-26_01:24:22
Locale: fr-FR (fr_FR); Calc: CL
Comment 2 Xisco Faulí 2017-08-04 08:19:33 UTC 
I can't reproduce it in

Version: 6.0.0.0.alpha0+
Build ID: 3f16306964d5bb81dda3c681bcabbacadf424e7b
CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group

nor gtk

Win only ?
Comment 3 Telesto 2017-08-04 10:23:09 UTC 
(In reply to Xisco Faulí from comment #2)
Sorry, I should have been more precise. It's only broken in the LO 5.4. The question is: should this be fixed in the 5.4 branch or not.
Comment 4 Xisco Faulí 2017-08-06 15:28:18 UTC 
oh, I see, adding backportRequest then
Comment 5 Adolfo Jayme Barrientos 2017-08-08 12:58:56 UTC 
Before using backportRequest, shouldn’t the relevant commit be identified first?
Comment 6 Xisco Faulí 2017-08-08 16:14:31 UTC 
(In reply to Adolfo Jayme from comment #5)
> Before using backportRequest, shouldn’t the relevant commit be identified
> first?

That's what backportRequest is meant for. Someone needs to bisect it, find the commit fixing this issue, and ask for a backport, in case it hasn't been done yet...