Skip to content

Optional filter text autocomplete support in chevron pop up#3336

Open
elsazac wants to merge 1 commit into
eclipse-platform:masterfrom
elsazac:ChevronAutocomplete
Open

Optional filter text autocomplete support in chevron pop up#3336
elsazac wants to merge 1 commit into
eclipse-platform:masterfrom
elsazac:ChevronAutocomplete

Conversation

@elsazac

@elsazac elsazac commented Sep 30, 2025

Copy link
Copy Markdown
Member

Refs : #194

This PR address one of the feature suggestion in #194.

This PR includes an autocomplete feature in the chevron popup filter, making it easier to navigate when too many editors are opened in the workbench. As the user types, matching editor names are suggested in the filter text area and the remaining part is auto-filled, improving speed and efficiency in locating editors.

This enhancement is implemented as an optional feature for the filter text in chevron pop up ie, users can enable or disable the autocomplete option based on their preference. A checkbox option to enable and disable the autocomplete behaviour is given in the Eclipse -> Settings -> General page. The feature is controlled through a new preference flag, ENABLE_AUTOCOMPLETE_IN_CHEVRON, stored under org.eclipse.ui.workbench. Users can enable or disable autocomplete in the Workbench Preferences, and when disabled, the chevron shows the normal standard filtering behaviour.

Key changes:

  1. Introduced a new optional autocomplete behaviour in the chevron popup to provide suggestions and auto completion.
  2. Normal text filtering is still available.
  3. Added a checkbox in Preference page to let users enable or disable the autocomplete option depending upon their preference.
  4. By default the option is disabled, but if the feature is to be enabled it can be done via Eclipse -> Settings -> General -> Enable autocomplete option in chevron popup
Optionalautocompleteoption.mov

@elsazac
elsazac force-pushed the ChevronAutocomplete branch 2 times, most recently from b49086d to 466b815 Compare September 30, 2025 08:44
@elsazac
elsazac marked this pull request as ready for review September 30, 2025 08:57
@github-actions

github-actions Bot commented Sep 30, 2025

Copy link
Copy Markdown
Contributor

Test Results

   855 files  ±0     855 suites  ±0   1h 3m 17s ⏱️ + 2m 27s
 8 120 tests ±0   7 877 ✅ ±0  243 💤 ±0  0 ❌ ±0 
20 262 runs  ±0  19 608 ✅ ±0  654 💤 ±0  0 ❌ ±0 

Results for commit 18e06d4. ± Comparison against base commit ce4e10f.

♻️ This comment has been updated with latest results.

@elsazac
elsazac force-pushed the ChevronAutocomplete branch from 466b815 to 897e653 Compare September 30, 2025 12:08
@elsazac
elsazac force-pushed the ChevronAutocomplete branch 6 times, most recently from 91d60f8 to 360601f Compare November 4, 2025 04:09
@elsazac
elsazac force-pushed the ChevronAutocomplete branch 3 times, most recently from 0a325e4 to 843fccb Compare November 12, 2025 13:16
@elsazac

elsazac commented Nov 13, 2025

Copy link
Copy Markdown
Member Author

@merks Would you be able to take a look at this?

@elsazac
elsazac force-pushed the ChevronAutocomplete branch 3 times, most recently from df177b0 to 3f43f46 Compare November 13, 2025 06:21
@elsazac
elsazac force-pushed the ChevronAutocomplete branch from 3f43f46 to 7d5f810 Compare December 16, 2025 14:47
@vogella
vogella force-pushed the ChevronAutocomplete branch from 7d5f810 to 39d3806 Compare April 27, 2026 09:06
@elsazac
elsazac force-pushed the ChevronAutocomplete branch from 39d3806 to fdee0e1 Compare June 23, 2026 16:46
@elsazac

elsazac commented Jun 23, 2026

Copy link
Copy Markdown
Member Author

@merks Would you mind reviewing this PR when you have a chance?

@elsazac
elsazac force-pushed the ChevronAutocomplete branch from fdee0e1 to 7c1b0b1 Compare June 24, 2026 04:46

@merks merks left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm concerned that the preference happens too quickly and not when the changes are applied by hitting Apply or OK. Please clarify the details around that.

@elsazac
elsazac force-pushed the ChevronAutocomplete branch 2 times, most recently from 7b80a1d to 66c210d Compare June 24, 2026 10:04
@merks

merks commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

I wanted to actually test it...

One thing I realized is had no idea about with the "chevron poup" actually refers to. I also wondered why anyone would ever not want this, i.e., why an option (and one where the user is unlikely to map the label of the option to something concrete in the UI.

Maybe @iloveeclipse, @HeikoKlare, or @sratz have opinions about whether this should be an option on just be the new default behavior always?

It seems cool and convenient, but the behavior is not exactly what I expected. I.e., when I was in this state below, I though hitting enter would choose the auto-complete value:

image

But it chooses whatever is selected down below, which is not unreasonable, but somehow inconvenient because I don't actually know how to "choose" the autocompleted value. There seem to be no way which somehow detracts from the usefulness...

@iloveeclipse

Copy link
Copy Markdown
Member

I've checked the feature and I think the extra code doesn't improve usability, it confuses more then it helps.

The (probably AI generated) feature desription says:

As the user types, matching editor names are suggested in the filter text area and the remaining part is auto-filled, improving speed and efficiency in locating editors.

Current behavior is that the popup list already filters the list and preselects first matching item "as the user types", so after typing few letters all what user needs is to hit "enter" - it is already as simple as it could be.

With the proposed extra code we also see the text for the already selected element in the text box, and that's it. Still hitting "enter" does same.

So what is the benefit of filling in the text in the text box? IMO this PR can be closed.

@elsazac
elsazac force-pushed the ChevronAutocomplete branch from 66c210d to f781ee1 Compare July 24, 2026 08:23
@elsazac
elsazac force-pushed the ChevronAutocomplete branch 2 times, most recently from 806eefe to d6555f3 Compare July 24, 2026 08:45
Add an optional Autocomplete support in chevron popup with preference
toggle in the
eclipse Settings->Preference->General page. Introduced a new
autocomplete behavior for the chevron popup filter text. As the user
types, matching editor names are suggested and the remaining part is
auto-filled, improving navigation efficiency within the chevron pop up.

Key changes:
- Added `chevronAutocompleteBehavior()` to implement auto completion
  with suggestion.
- Retained existing `normalFilterBehavior()` for plain text filtering
incase  the user wanted to disable the auto complete feature.
- Updated `installFilter()` to switch between behaviors based on user
  preference
- Added `isAutocompleteEnabled()` method to check the preference state
@elsazac
elsazac force-pushed the ChevronAutocomplete branch from d6555f3 to 18e06d4 Compare July 24, 2026 09:59
@elsazac

elsazac commented Jul 24, 2026

Copy link
Copy Markdown
Member Author

Thanks @merks for testing this. apologies for the delayed response. I had been away for a while and am only now getting around to addressing everything.

and one where the user is unlikely to map the label of the option to something concrete in the UI.

I agree that the name "chevron popup" isn't very understandable from a user POV as many might not be even be familiar with the name. If you have a suggestion for a more relevant one, i can update that.

But it chooses whatever is selected down below, which is not unreasonable, but somehow inconvenient because I don't actually know how to "choose" the autocompleted value. There seem to be no way which somehow detracts from the usefulness...

What I had been doing was pressing the right arrow key to accept the autocomplete text first, and then pressing enter to get the item. I hadn't really considered the possibility of using enter directly to accept the autocomplete suggestion, but your comment made me realize that it makes sense and is probably what users would naturally expect. so I have updated the code accordingly. I would appreciate it if you could give the updated code another try. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants