Bug 108322 - Unexpected icon set behavior
Summary: Unexpected icon set behavior
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.3.3.1 rc
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 108321 (view as bug list)
Depends on:
Blocks: Conditional-Formatting
  Show dependency treegraph
 
Reported: 2017-06-03 12:03 UTC by Michael Meeks
Modified: 2023-07-21 05:21 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 Michael Meeks 2017-06-03 12:03:17 UTC
I enter 1, 2, 3 into A1:A3, I click the toolbar icon-set button and select three traffic lights, or arrows - all of the items are green, or up-arrows or ...

Changing the data to say 0, or -1000, or 0.0001 leaves all of the icons green.

In Excel - the same work has eg. a red/down for A1, a yellow right for A2, and a green up for A3 (or equivalent traffic lights).

Markus - any ideas where to poke to fix this ? I assume (as with the data bars) that these guys need to adjust to the range of the data in there ? (there seem to be no extra / magic options I can see to tweak this).

Thanks !
Comment 1 Michael Meeks 2017-06-03 12:03:36 UTC
*** Bug 108321 has been marked as a duplicate of this bug. ***
Comment 2 m_a_riosv 2017-06-04 16:58:07 UTC
It happens with default values (zero) for both comparisons, what I think is right.
But with 1st >= 40 and 2ΒΊ >= 70 (as percent) works fine for me.
BTW comparison values are reset every time the icon set type is modified.
Comment 3 QA Administrators 2018-06-05 02:38:18 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2020-06-05 03:46:02 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2022-06-06 03:26:55 UTC
Dear Michael Meeks,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug