Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

🐞 Lag when selecting certain settings menus

Open
#1,734 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue names no files or tests. First reproduce the lag in the settings menu on the reported macOS and CodeEdit versions, comparing the responsive Terminal/Locations navigation with General, Navigation, Themes, and Text Editing; done means arrow-key navigation between all settings menus is responsive without a noticeable pause.

Written by the indexing model from the issue text.

Description

bug performance settings UI UX
Description

When using the arrow keys to navigate between the settings menu, there is a noticeable lag when selecting these four menus: General, Navigation, Themes, Text Editing. This does not happen with the other settings menus, as they load in quickly are responsive.

To Reproduce
  1. Open the settings menu
  2. Select the Terminal menu
  3. Using your arrow keys, quickly navigate between the Terminal and Locations menus. Notice how responsive it is.
  4. Now navigate throughout the rest of the menu and notice there is a pause between selecting the mentioned settings menus.
Expected Behavior

There can't be lag when quickly navigating between settings menus.

Version Information

CodeEdit: 0.1.0-dev
macOS: 14.4.1
Xcode: 15.3

Additional Context

No response

Screenshots

Hard to see when you can't see my key presses, but the lag starts appearing after selecting the Text Editing menus and beyond.
https://github.com/CodeEditApp/CodeEdit/assets/29493784/9983b9ac-1239-4a92-8598-7a735f534141

Dominant language
Swift
Stars
23.1k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeEditApp/CodeEdit

All issues in CodeEditApp/CodeEdit

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.