Bug 119069 - lSmoth navigation
Summary: lSmoth navigation
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.0.5.2 release
Hardware: x86-64 (AMD64) All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-02 17:49 UTC by jim
Modified: 2019-05-08 20:42 UTC (History)
1 user (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 jim 2018-08-02 17:49:20 UTC
Description:
I can't find a complement page so:

NEVER cave in to the ribbon concept.
1. Uses valuable real estate.
2. Actually takes just as long to use. 

Steps to Reproduce:
Click on command bar item

Actual Results:
program responds

Expected Results:
p[orgram responds


Reproducible: Always


User Profile Reset: No



Additional Info:
nothing.
Comment 1 Jean-Baptiste Faure 2018-08-03 08:34:23 UTC
What do you mean ? Could you be more clear?

Status set to NEEDINFO, please set it back to UNCONFIRMED once requested
informations are provided.

Best regards. JBF
Comment 2 QA Administrators 2019-03-21 11:12:06 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2019-05-08 20:42:16 UTC
Dear jim,

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