# Combo box content is hidden behind the popup window

**URL:** <https://community.sonarsource.com/t/combo-box-content-is-hidden-behind-the-popup-window/183358>\
**Category:** SonarQube Server / Community Build\
**Tags:** ui, sonarqube\
**Created:** [June 8, 2026, 2:11pm UTC](https://community.sonarsource.com/t/combo-box-content-is-hidden-behind-the-popup-window/183358 "2026-06-08T14:11:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![magyarimiki](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/magyarimiki/32/75216_2.png) [@magyarimiki](https://community.sonarsource.com/u/magyarimiki)\
**Post date:** [June 8, 2026, 2:11pm UTC](https://community.sonarsource.com/t/combo-box-content-is-hidden-behind-the-popup-window/183358/1 "2026-06-08T14:11:47Z")

</div>

I’m working with Sonarqube Community 26.6.

I try to change the quality profile for a certain language to a custom profile, and when I open the combo box, the list of options are shown **behind** the popup window and of course I cannot choose.

I needed to create five or six QPs to realize this issue, otherwise the popup completely overlapped the list and it seemed to be an irresponsive combo box.

The browser is Edge on Windows 11.  
I had the same issue on 26.5 as well.

 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/5/a/5afda9232995137803e2585cb932cc06fbf7b8c8.png)

---

<div class="post-metadata">

**Author:** ![andres](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/andres/32/76342_2.png) [@andres](https://community.sonarsource.com/u/andres)\
**Post date:** [June 10, 2026, 7:28am UTC](https://community.sonarsource.com/t/combo-box-content-is-hidden-behind-the-popup-window/183358/6 "2026-06-10T07:28:22Z")

</div>

Hello @magyarimiki, thanks for reaching out! I can see that you found [the other thread where this was originally reported](https://community.sonarsource.com/t/cannot-change-quality-profile-of-a-project/182033/10), and my colleague David replied to you there. Reiterating here for completeness sake: the fix will be released with version 26.7, planned for July 6th.
