Bug 157952

Summary: Content Control layout: dropdown indicator does not disappear moving from combobox to text control
Product: LibreOffice Reporter: Justin L <jluth>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: NEW ---    
Severity: trivial CC: ilmari.lauhakangas, jluth
Priority: medium Keywords: implementationError, notBibisectable
Version: unspecified   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:
Bug Depends on:    
Bug Blocks: 107742    
Attachments: SDT-showingDropdownArrow.docx: reverse-tab and see the hanging dropdown
SDT-showingDropdownArrow.docx: reverse-tab and see the hanging dropdown

Description Justin L 2023-10-27 18:45:01 UTC
Created attachment 190456 [details]
SDT-showingDropdownArrow.docx: reverse-tab and see the hanging dropdown

Steps to reproduce with SDT-showingDropdownArrow.docx
-press shift-tab to switch to the last control (the date control)
-press shift-tab again - moving to plaintext. (down arrow on date control still)
-press shift-tab again - moving to dropdown (down arrow moved to dropdown)
-press shift-tab again - moving to rich text (down arrow on dropdown still)

The down arrow disappears when moving the cursor anywhere OTHER THAN another content control (can also be seen with checkboxes for example).

Probably an implementation error. Date content controls already exist in 7.0, but other content controls (like the easy to reproduce with text controls) don't show up until around 7.4 - where the implementation error can finally be noticed.
Comment 1 Justin L 2023-10-27 18:58:23 UTC
Created attachment 190457 [details]
SDT-showingDropdownArrow.docx: reverse-tab and see the hanging dropdown
Comment 2 Buovjaga 2023-11-02 18:43:47 UTC
Reproduced with document.

Arch Linux 64-bit, X11
Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 6abe70d181e764c962a9c5e85e826247650bab3a
CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 1 November 2023
Comment 3 Justin L 2023-11-02 18:55:26 UTC
It is not a DOCX specific bug, just a DOCX provided example.