apache / apache/netbeans

Shift-Escape malfunction

Open
#8,350 4 comments 0 reactions 0 assignees View on GitHub
kind:bug UI
Dominant language
Java
Stars
3.1k
Forks
935
Avg merge
2d 3h
Merged PRs (30d)
17

Description

### Apache NetBeans version

Apache NetBeans 24

### What happened

at the press of the keys "shift-esc" to maximize window unpredictable things happen:

- sometimes when focus is on source code editor nothing happen
- if focus is on source code editor

https://github.com/user-attachments/assets/09d880d0-3691-4c66-b7fc-0d78917cb2f0

and press "shift-esc", at the second pression of "shift-esc" the left panel and the bottom panel both show the last tab
- sometimes the search results panel is all wrong

### Language / Project Type / NetBeans Component

java

### How to reproduce

- open a new search from left panel
- search for something, and the bottom panel opens
- focus on another tab in the bottom panel, near the search result
- focus on the source code editor
- press shift-esc twice
- focus on the search results panel
- the search results panel is all wrong

### Did this work correctly in an earlier version?

No / Don't know

### Operating System

debian

### JDK

17

### Apache NetBeans packaging

Apache NetBeans provided installer

### Anything else

_No response_

### Are you willing to submit a pull request?

No

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the Shift-Escape sequence in Apache NetBeans 24 on Debian with JDK 17, including the source editor, bottom panel, and search results panel. Investigate the behavior around maximizing the window and panel tab state; done means repeated Shift-Escape presses leave the panels and search results correctly displayed.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
desktop, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.