Bug 124945 - Minor UI glitch: color of selected item in drop down list
Summary: Minor UI glitch: color of selected item in drop down list
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: iOS Editor (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other iOS
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-25 07:29 UTC by Nicolas Christener
Modified: 2023-09-21 03:15 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Color of the selected item too dark (406.95 KB, image/png)
2019-04-25 07:30 UTC, Nicolas Christener
Details
iOS uses a check mark to show which element is selected (828.61 KB, image/png)
2019-04-25 07:32 UTC, Nicolas Christener
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Christener 2019-04-25 07:29:12 UTC
Description:
The color of a selected item in a drop down list in the iOS app has a color which doesn't fit the rest of the color scheme. It's a dark blue and I suggest to change it to a friendlier blue (maybe a bit brighter than the blue which is used elsewhere in the app) or only use a check mark (✓) - like iOS does in other situations - do mark the selected item.


Steps to Reproduce:
1. Open a "tunneled dialog"
2. Tap on a drop down list

Actual Results:
The selected element is highlighted using a dark blue color.

Expected Results:
The color should be brighter or the selected item should be marked with a check mark (✓)


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Nicolas Christener 2019-04-25 07:30:44 UTC
Created attachment 150996 [details]
Color of the selected item too dark
Comment 2 Nicolas Christener 2019-04-25 07:32:28 UTC
Created attachment 150997 [details]
iOS uses a check mark to show which element is selected
Comment 3 Aron Budea 2019-04-25 12:49:17 UTC
It's dark indeed.
Comment 4 QA Administrators 2021-09-20 03:40:10 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2023-09-21 03:15:45 UTC
Dear Nicolas Christener,

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