Skip to content

Use dialog font in editor drop-down and drop bold-when-hidden marker#3940

Open
vogella wants to merge 1 commit intoeclipse-platform:masterfrom
vogella:editor-dropdown-dialog-font
Open

Use dialog font in editor drop-down and drop bold-when-hidden marker#3940
vogella wants to merge 1 commit intoeclipse-platform:masterfrom
vogella:editor-dropdown-dialog-font

Conversation

@vogella
Copy link
Copy Markdown
Contributor

@vogella vogella commented Apr 28, 2026

The chevron drop-down on editor stacks inherited the SWT system font, which on many platforms looks out of place compared to the rest of the IDE chrome. This change switches both the filter text and the result table to JFaceResources.getDialogFont() so the list matches the Quick Switch Editor (Ctrl+E) dialog.

It also removes the rule that rendered an entry in bold when its CTabItem was not currently visible in the tab bar. That marker is undiscoverable (no legend, and bold conventionally signals importance/unread/modified, none of which apply), redundant with why the drop-down is opened in the first place, and visually conflicted with the more useful match highlighting introduced in #3938.

The editor chevron drop-down inherited the SWT system font, which on
many platforms looks out of place compared to the rest of the IDE
chrome. Switch the filter text and the table to JFaceResources
getDialogFont() so the list matches the Quick Switch Editor (Ctrl+E)
dialog and other workbench dialogs.

Also remove the rule in BasicStackListLabelProvider that rendered an
entry in bold when its CTabItem was not currently visible in the tab
bar. That marker is not useful to users:

  - It is undiscoverable. There is no legend or tooltip explaining
    that bold means "tab scrolled off the visible tab bar". Bold
    conventionally signals importance, unread, or modified, none of
    which apply here.
  - It is redundant with why the drop-down is opened. Users open the
    chevron precisely because some tabs do not fit. Encoding which
    rows overflowed burns the strongest typographic emphasis on
    information the user did not ask for.
  - It crowds out more meaningful styling. PR eclipse-platform#3938 introduces bold
    for matched filter substrings, which is a far more useful signal
    and conflicted visually with the previous all-bold rows.
@vogella
Copy link
Copy Markdown
Contributor Author

vogella commented Apr 28, 2026

Old:

image

New (light):

Screenshot From 2026-04-28 10-53-28

New (dark):

image

The existing CTRL+E style which is unchanged would also in line with the new font

image

@BeckerWdf
Copy link
Copy Markdown
Member

You are mixing two changes. The font size and the bold-stuff. I think the one thing (size) is clear. The other one can be discussed. Should this be split into two PRs?

@vogella
Copy link
Copy Markdown
Contributor Author

vogella commented Apr 28, 2026

You are mixing two changes. The font size and the bold-stuff. I think the one thing (size) is clear. The other one can be discussed. Should this be split into two PRs?

I do not change the font size in this PR, please check the code. It looks bigger because it is bold (and not the dialog font)

@BeckerWdf
Copy link
Copy Markdown
Member

But your PR text say:

The chevron drop-down on editor stacks inherited the SWT system font, which on many platforms looks out of place compared to the rest of the IDE chrome. This change switches both the filter text and the result table to JFaceResources.getDialogFont() so the list matches the Quick Switch Editor (Ctrl+E) dialog.

@vogella
Copy link
Copy Markdown
Contributor Author

vogella commented Apr 28, 2026

But your PR text say:

The chevron drop-down on editor stacks inherited the SWT system font, which on many platforms looks out of place compared to the rest of the IDE chrome. This change switches both the filter text and the result table to JFaceResources.getDialogFont() so the list matches the Quick Switch Editor (Ctrl+E) dialog.

Yes, that is also what I said here: It looks bigger because it is bold (and not the dialog font)
So you are suggesting to split the PR by the usage of the dialog font from the bold removal?

@github-actions
Copy link
Copy Markdown
Contributor

Test Results

   852 files  ±0     852 suites  ±0   53m 35s ⏱️ + 1m 31s
 7 920 tests ±0   7 677 ✅ ±0  243 💤 ±0  0 ❌ ±0 
20 262 runs  ±0  19 607 ✅ ±0  655 💤 ±0  0 ❌ ±0 

Results for commit 7720790. ± Comparison against base commit 284a9f8.

@iloveeclipse
Copy link
Copy Markdown
Member

I can't spot a difference because every old/new pair of screenshots shows different dialogs, and the light one shows even dark mode??? Sorry, it just wastes everyone time. Can you please provide clean side by side examples before / after?

@tomaswolf
Copy link
Copy Markdown
Member

Leave the bolding. It is important information, and I rely on it quite frequently. I find it very useful to see immediately which of the items is in a visible tab.

@iloveeclipse
Copy link
Copy Markdown
Member

Leave the bolding. It is important information, and I rely on it quite frequently.

Correct. If this is not in Ctrl+E it should be added there, not otherwise.

@vogella
Copy link
Copy Markdown
Contributor Author

vogella commented Apr 28, 2026

Leave the bolding. It is important information, and I rely on it quite frequently. I find it very useful to see immediately which of the items is in a visible tab.

So you need a visual distinction between open and not open. I see if I can come up with something that serves this purpose and does not look misplaced in the current ui (or even ugly) to me. I will copy you in the PR if I create one and will wait for your feedback.

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.

4 participants