Bug 117124 - Item of notebook toolbar has no KeyID.
Summary: Item of notebook toolbar has no KeyID.
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.1.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 115131
  Show dependency tree / graph
 
Reported: 2018-04-20 12:49 UTC by baffclan
Modified: 2018-05-29 09:11 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Screenshot (22.11 KB, image/png)
2018-04-20 12:51 UTC, baffclan 		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 baffclan 2018-04-20 12:49:59 UTC 
Description:
Item of notebook toolbar has no KeyID.

Steps to Reproduce:
1. Add a "Toolbar Layout" item in Menu(Menu -> Tools -> Customize)
2. Menu -> View -> Toolbar Layout


Actual Results:  
No KeyID

Expected Results:
have KeyID


Reproducible: Always


User Profile Reset: No



Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Comment 1 baffclan 2018-04-20 12:51:19 UTC 
Created attachment 141500 [details]
Screenshot
Comment 2 raal 2018-04-21 15:54:04 UTC 
I can confirm with Version: 6.1.0.0.alpha0+
Build ID: b11188835d3b87cd9d2a8cdb3da204cfda5d3e6e
CPU threads: 4; OS: Linux 4.4;UI render: default; VCL: gtk2; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2018-04-20_21:52:47
Comment 3 baffclan 2018-05-21 04:42:39 UTC 
Cannot reproduce with LibO 6.1 master(x64) on Windows10 pro

Version: 6.1.0.0.alpha1+ (x64)
Build ID: ea33ae5ef0a9d6b03fdef6503066100d0ae12729
CPU threads: 4; OS: Windows 10.0; UI render: default; 
TinderBox: Win-x86_64@62-TDF, Branch:master, Time: 2018-05-03_14:09:58
Locale: ja-JP (ja_JP); Calc: group
Comment 4 Xisco Faulí 2018-05-29 09:11:18 UTC 
Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.