Bug 155295 - Content control field should look the same after select/unselecting the combo option
Summary: Content control field should look the same after select/unselecting the combo...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.6.0.0 alpha1+
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: DOCX-Content_Control
  Show dependency treegraph
 
Reported: 2023-05-14 12:40 UTC by Hossein
Modified: 2025-05-17 03:12 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Effect of select/unselect in LibreOffice (5.15 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2023-05-14 12:40 UTC, Hossein
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Hossein 2023-05-14 12:40:43 UTC
Created attachment 187266 [details]
Effect of select/unselect in LibreOffice

Description:
The attachment provides an example content control field that is a combo box with several options, and a placeholder text.
After selecting/unselecting the combo option, the content control field should look the same as before, but it will not.

Steps to Reproduce:
1. Open the attached DOCX‌ file.
Note: First line contains a combo box, selected and unselected in LibreOffice. Second line contains the combo box that is not selected and unselected in LibreOffice. Third line is also untouched, just like the second one, for the reference.
2. Select the combo box from the second line. Select and unselect it. You can not go back to what it was before. Compare the color to the 3rd line for the reference.

Actual Results:
Color and behavior of selected/unselected lines are different from the untouched combo box like the 3rd line.

Expected Results:
Color and behavior of the all the lines should be the same as before.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 35dca0ad624586c490bad612de0010c3bb228565
CPU threads: 12; OS: Linux 5.19; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: CL threaded
Comment 1 Buovjaga 2023-05-17 13:33:04 UTC
I reproduce the change in colour

Arch Linux 64-bit, X11
Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 85a47bbb8340e65a19dc1ceaac768902a771ee77
CPU threads: 8; OS: Linux 6.3; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 17 May 2023
Comment 2 QA Administrators 2025-05-17 03:12:23 UTC
Dear Hossein,

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