[Bug] No keyboard input upon launching application macOS Sonoma 14.2

[w269219808]

Description

No keyboard input upon launching application

Environment

• OS: [e.g., macOS 14]
• Ferrite version: [Ferrite v0.2.7]
• Rust version: [run rustc --version]
• Installation method: [pre-built binary / built from source]

Steps to Reproduce

1. Go to '...'
2. Click on '...'
3. Type '...'
4. See error

Expected Behavior

What you expected to happen.

Actual Behavior

No keyboard input

[OlaProeis]

Hi @w269219808 Thank you for reporting this.

What We Know

This is very likely related to a known class of input issues in winit 0.29.x (the windowing library Ferrite uses via egui/eframe 0.28). We've already received a similar report for Linux/Wayland (#106) where keyboard input doesn't work at all, and the root cause was traced to the winit input pipeline.

For macOS Sonoma specifically, Ferrite has no custom keyboard handling code, all keyboard events flow through:
macOS → winit 0.29 → egui 0.28 → Ferrite editor

If winit doesn't deliver the events correctly, no typing reaches the editor.

Fix Plan

We're already tracking an egui/eframe upgrade to 0.31+ (which brings winit 0.31+ with substantially rewritten input handling across all platforms) as an internal high-priority task. This upgrade is expected to resolve keyboard issues on macOS Sonoma, just as it will fix the Wayland issue reported in #106.

Could You Help Us Narrow It Down?

To better understand the issue, could you provide some additional details?

1. Scope of the issue:

   • Is it all keyboard input (including shortcuts like Cmd+O, Cmd+Q)?
   • Or only typing in the editor (shortcuts still work)?

2. Focus behavior:

   • Does clicking inside the editor area before typing help?
   • Does Alt+Tab away and back fix it?

3. Accessibility settings:

   • Do you have any accessibility features enabled that might affect input?

4. Build method:

   • Are you using the pre-built .dmg or building from source?
   • If pre-built, did macOS show any Gatekeeper warnings when first opening?

5. Reproducibility:

   • Does this happen every launch, or intermittently?

This information will help us determine whether this is purely the winit/egui upstream issue or something specific to Ferrite's focus management on macOS.

Related Issues

• [Bug] No keyboard input upon launching application Ubuntu 24.04 LTS #106 Same symptom (no keyboard input) on Ubuntu 24.04 Wayland, confirmed as winit 0.29 backend bug

Thank you for the report, we'll update this issue when the egui/eframe upgrade lands!