@copilot Why do you think CTRL - works but CRTL = need this change?

@copilot Why do you think CTRL - works but CRTL = need this change?

The difference is in how each key is handled inside GraphicsWindow::KeyboardEvent:

Ctrl-minus: The ZOOM_OUT accelerator is bound to bare '-' (no Ctrl). When Ctrl-minus arrives, event.controlDown = true, so it doesn't match the accelerator (which expects controlDown = false). No handler claims it → KeyboardEvent returns false → KeyboardCallback returns EM_FALSE → browser sees it and decreases font size. ✓

Ctrl-=: There's a special-case handler at graphicswin.cpp:249 that matches event.chr == '=' without checking controlDown:

} else if(event.chr == '=') {
    // Treat = as +.
    MenuView(Command::ZOOM_IN);
    return true;
}

This fires for both bare = and Ctrl-=, returning true both times. So KeyboardCallback returns EM_TRUE → the browser never sees Ctrl-= → font size increase is blocked. ✗

The fix in guihtml.cpp short-circuits before the event even reaches GraphicsWindow::KeyboardEvent when Ctrl-= is pressed, letting the browser handle it.

Probably the other option would have been cleaner, but this is minimal and non-intrusive.

Its been 3 hours since I pushed and this doesn't seem to do anything. ;-(

@phkahler yes, it has not updated (the easiest way to check is Help | Go to GitHub commit). It goes to 289651e, while the CTRL+ change is 08fdb35.

I do not know why. Perhaps a rate limiting logic @jwesthues put in?

The CI ran normally and the site responded "good" https://github.com/solvespace/solvespace/actions/runs/24147131706/job/70465587468#step:6:77

The time stamp is "Wed Apr 8 13:00:03 EDT 2026"

The problem is I'm not on a PC and I do not know how to check exact commit time stamps on GitHub.

Weird, and not any deliberate rate limiting and not the Cloudflare cache. The CI says it succeeded at 09:55 PDT = 12:55 EDT, /pull-webver.pl got hit at 12:55:41 EDT, and the download happened at 13:00:03 EDT per above; so those all seem correct. Is it possible that the download doesn't work immediately after the CI completes and I need to deliberately wait? I see some unofficial reports of delays in GitHub's CDN.

I re-triggered the download and it worked this time. I've added more logging so that I can debug this better if/when it recurs, but haven't added the delay yet.