Triage of 548 open Bug tickets: those with no comment or check-in from me on 2026-09-24, plus 38 added on 2026-10-04 (filed since then, Pending then, or reopened; 16 of them filed by me), plus 68 added on 2026-10-22 (all other open or Pending Bug tickets not filed by me: the 30 created before 8.5, 31 I had already worked on, and 7 filed or missed since 10-04). Reproduced on Linux/X11 under Xvfb (main 9.1 tip, 9.0, 8.7, 8.6 tip, 8.5, 8.4) and on a Windows 11 VM (9.1, 8.6, 8.5, 8.4). Rows marked patch link to a prototype patch (150 in all, in tk-triage/prototypes). Updated 2026-11-11 with what happened since: the emoji before each ticket id shows its progress. On 2026-10-24 every prototype for a still-open ticket was verified again on current main, on Linux and Windows, and given a test where practical; on 2026-10-25 seven more reproduced tickets got prototypes.
Status now: Open
NOT-REPRODUCED (9.1 main)
Status now: Open
NOT-REPRODUCED (9.1 main, 8.6 tip; MSVC, Win11, 100% scaling)
make test runs tests/all.tcl and tests/ttk/all.tcl in separate processes on both win/Makefile.in and makefile.vc, so the classic suite cannot leave in-process state behind. Only system state could carry over (pointer position, focus, leftover windows). The failing tests (heading and row height, keyboard events) depend on metrics, and nemethi reports a clean run at 100% display scaling, so a scaling β 100% is the more likely factor.
tk scaling) for the failing runs; nemethi sees no failures at 100%.
tk scaling and whether the failures persist with an MSVC build or at 100% scaling.
NOT-REPRODUCED (all tested)
-O2 build and --enable-symbols build, test alone and after the a*/b*/canv* test files with the failsOnCILinux constraint enabled. All give 98 171 302 202, and valgrind is clean.
NOT-REPRODUCED (Win11 VM, 9.1 main ref); prototype builds and passes tests
||| mode). On this VM a different intermittent failure, |<Leave> .<Enter> .||, happens 2/11 runs without the patch and 3/10 with it. The patch does not fix that mode.
||| in 11 event.test runs / after: no ||| in 10 runs. The other mode occurs at the same rate.
<Enter> comes from the pointer being seen at the old position during the same update, probably a stale WM_MOUSEMOVE or the mouse timer.
NOT-REPRODUCED (9.1 main, Microsoft Print to PDF)
tk print .c, and asks you to check the PDF from "Microsoft Print to PDF" for the 3 texts.
count >= 3 GdiParseFontWords always runs, so weight and slant are applied. A negative size becomes lfHeight = siz in logical units. After _gdi map those logical units are canvas pixels, which is why _make_gdi_cfont converts points to negative pixels on purpose. If text really is missing, the cause is somewhere else, for example the _gdi text path or the map/extent.
_gdi map. GdiMakeLogFont still parses weight/slant for any size. Can you attach a minimal script and say which printer or driver you used, and whether the text is missing with "Microsoft Print to PDF" too?
{Helvetica -32 bold roman}, {Courier -16 normal roman} and {Arial -16 normal italic}. 8.6 has no tk print.
Side finding: "Courier 12" printed in a sans-serif substitute, because font actual returns the raster "Courier" (see 3249f7d4c6), which the printer DC doesn't have. The 3249f7d4c6 prototype would make it "Courier New".
NOT-REPRODUCED (revised_text tip 8b6e012e5d, X11)
data->maxX = MAX(data->width, data->x) is set without checking TEXT_WRAPMODE_NONE. By contrast, line 3263 sets maxX = -1 for wrap none. With a positive maxX, the tab code applies desired %= data->maxX. I could not trigger this path.
NOT-REPRODUCED (9.1 main, 8.6 tip; MSVC 2022, Win11)
win constraint. The repro script win/8972b57276.tcl runs the bodies of winWm-7.3 and wm-attributes-1.5.1/1.5.2/1.5.4 and prints PASS/FAIL plus a verdict. I sanity-ran it on X11 8.6, where it passes.
GetNextWindow(oldWrapper, GW_HWNDPREV). That fails if the window above is not a Tk wrapper, e.g. a console or IME window. This is probably environment-dependent rather than VC6-specific, but that needs checking against a modern MSVC build on the same machine.
One unrelated failure: winWm-7.4 ("UpdateWrapper must maintain focus", result .t .) fails on 8.6 in both runs, and on 9.1 only when run on its own. It passes in the full 9.1 file. This is probably focus-stealing rules, because the tests ran from a scheduled task.
NOT-REPRODUCED (main, 9.0, 8.6 tip, 8.6.14)
selection = {} in <<TraverseIn>> and afterwards. .tv focus stays I002, which is expected: the focus item is not the selection.
selection is empty. focus still returns the item, which is expected. Please attach a self-contained Tcl or tkinter script if it still happens.
NOT-REPRODUCED (revised_text tip 8b6e012e5d and d6295a4f0d from before the -lang to -locale change), but only with a synthetic example; the original scidb example could not be fetched (offline)
\+ soft hyphens for trema (nl), doubledigraph (hu), repeathyphen (pl) and doublevowel (nl) words, window resized 1 px at a time from 500 down to 30 px. No assertion fired.
segPtr == endOfLineSegPtr || segPtr == endOfTextSegPtr for segments with no sectionPtr that are not hyphen segments). It probably fires on a temporary segment made for the spelling-change hyphen rules.
NOT-REPRODUCED (X11); CANNOT-TEST (macOS)
.tt.u sync or count -update before counting would be the obvious hardening).
.tt.u sync before the count might fix it.
Status now: Closed (Fixed)
aqua-right-click-target, in main, 9.0: Fix 061f633f43: MacOS aqua: <<ContextMenu>> binding sometimes triggers for incorrect toplevel. Clicking with the right or middle button does not make the windNOT-REPRODUCED (X11: main, 8.6). The Aqua Button-2/3 part is CANNOT-TEST (macOS).
., then in .b twice, then B1 in each). Tested with main and 8.6 under no WM, icewm, openbox and fvwm. Each ButtonPress always went to the clicked toplevel with correct %x/%y. (icewm does not move focus on B3, but the event still goes to the right window.)
Status now: Pending
NOT-REPRODUCED (all tested)
make -j8 install-libraries INSTALL_ROOT=... three times. tk.tcl always went to <prefix>/lib/tk9.1/tk.tcl. unix/Makefile.in installs it only to $(SCRIPT_INSTALL_DIR)=$(TK_LIBRARY)=<libdir>/tkX.Y, which is fixed.
$(libdir)/tk8.6 (TK_LIBRARY), and repeated parallel installs are deterministic here. The remaining problems were in the Spack environment (TCLLIBPATH). Closing.
NOT-REPRODUCED (9.1 main, 8.6 tip, Windows 11)
Status now: Closed (Fixed)
panedwindow-identify-bounds, in main, 9.0: panedwindow identify: report the sash only for its own pixels. The far bounds of the sash and the handle were inclusive, and a handle wider than the sash was cotrunk, in main, 9.0, 8.6: See: ac7f771957: panedwindow identify: report the sash only for its own pixelspanedwindow-sash-cursor, in main: See ac7f771957: panedwindow sash cursor: set it also when the pointer enters on the sash, keep it while the sash is dragged, and forget the cursor state of a core-9-0-branch, in main, 9.0: See ac7f771957: panedwindow identify: report the sash only for its own pixels (backport of 23aa8b82e3)core-8-6-branch, in 8.6: See ac7f771957: panedwindow identify: report the sash only for its own pixels (backport of 23aa8b82e3)trunk, in main, 9.0: Fix for ac7f771957: tk panedwindow: cursor changing code does not work wellcore-9-0-branch, in 9.0, 8.6: Fix for ac7f771957: tk panedwindow: cursor changing code does not work wellcore-8-6-branch, in 8.6: Fix for ac7f771957: tk panedwindow: cursor changing code does not work wellpanedwindow-sash-cursor, in main: Rebase to mainfossil merge --force because the panedwindow-identify-bounds leaf had already been closed. I think we would be wise not to rusn too much with these fixes.) Anyway, that fixed the problem of the cursor reverting to the pointer during the drag. The only remaining issue that I saw was that sometimes the push-me-pull-you cursor β¦NOT-REPRODUCED (main, 9.0, 8.6 on X11); Aqua CANNOT-TEST
event generate -warp (XWarpPointer, not XTEST). Moving from the sash into a pane sends <Leave> .pw NotifyInferior, and the sash cursor is reset at once (cget -cursor is "" after 30 ms); the 150 ms timer never matters. .pw identify and winfo containing agree on every sash pixel, so a press under the sash cursor always reaches the panedwindow. The generic emulation (generic/tkPointer.c GenerateEnterLeave β TkInOutEvents) also queues NotifyInferior crossings, so Windows should behave like X11 (untested). Marc's 2020 analysis points to macOS sub-pixel pointer rounding. bll's branch bug-ac7f7719 (one commit, 2020) is unmerged. It uses a single global Priv(panedwindowname), which breaks with several or nested panedwindows, and it rewrites the children's bindtags.
identify while Button delivery follows the stacking order. They agree on X11; per 6b51f22bff they can disagree on Aqua.
Status now: Closed (Works For Me)
NOT-REPRODUCED (9.1 main, 8.6 tip, Windows 11, vista theme)
-fill both into a taller parent paints fully after resizing. The issue does not exist on X11.
Combobox.border/Combobox.background vsapi parts may not paint the whole parcel when the widget is taller than the native combobox, so the unpainted area keeps stale pixels.
-fill both in a taller frame, then resize or minimize and restore.
-fill both in a 160β220 px tall frame). It captures the combobox area after the initial draw, after enlarging, after shrinking, and after iconify plus deiconify. All captures show a clean white field with the arrow, and no black pixels apart from the text. Win10 was not tested.
NOT-REPRODUCED (all WMs available here); CANNOT-TEST on GNOME/mutter (the installed mutter 50 is Wayland-only and cannot run as an X11 WM)
normal and mapped.
Status now: Closed (Fixed)
NOT-REPRODUCED for 44.7, 44.8, 45.2 and 45.4 (they pass under every WM). unixWm-4.1β4.3 still fail on main under metacity (GNOME family), as the ticket expects for gnome3/unity.
NOT-REPRODUCED (all tested). Not a Tk bug: it depended on the fontconfig version.
font actual F -family Ε
returns the test font itself, and font measure gives the narrow advance (8 px vs 28 px for "a"). There is no fallback, even in 8.6.8.
NOT-REPRODUCED (revised_text tip 8b6e012e5d, 2026-09-15). The report was a single occurrence with no reproducer.
Status now: Open
NOT-REPRODUCED (9.1 main, vista theme, 133% scaling)
identify element and prints PASS/FAIL.
NOT-REPRODUCED (per serhiy.storchaka 2026-09-18 on 8.6.4, 8.6.18 and main). I could not re-check it here: the Thread package is not installed for the 8.6 and main builds.
puts, but Thread was missing.
update, fixed by the Tcl 8.6.7 event-queue rework (Tcl 68698a3ac4).
NOT-REPRODUCED (all tested)
make test with no WM: spinbox.test and raise.test pass (the 28 failures elsewhere come from having no WM). spinbox.test run twice each under fvwm, icewm and openbox: spinbox-19.8, 19.10 and 19.14 always pass. spinbox-5.7 failed once under fvwm, which is an unrelated one-off. KDE could not be tested because kwin_x11 is not installed and mutter would not start.
make test or under fvwm, icewm and openbox. The failures were caused by focus events from user activity during the run. Suggest closing as works-for-me.
NOT-REPRODUCED (all tested)
make test with no WM, plus raise.test twice each under fvwm, icewm and openbox: raise-1.1 always passes.
NOT-REPRODUCED (9.1 main, 8.6 tip, Windows 11)
wm geometry resize is also fine.
destroy triggers UpdateGeometryInfo during the modal size loop.
NOT-REPRODUCED (serhiy, 2026-09-19: dead keys keep working after tk_getOpenFile, posting a menu, grabs and focus changes)
NOT-REPRODUCED (all tested)
Status now: Pending
NOT-REPRODUCED (all tested, with the local Xlib input method)
setxkbmap fr. Real XTEST key events (dead_circumflex, then e) were sent to 2 and 3 entries plus texts, all fields were cleared, and the typing was repeated. Every field got "Γͺ" in both rounds, without a WM (twm did not start).
Status now: Pending
NOT-REPRODUCED (all tested)
Status now: Closed (Out of Date)
NOT-REPRODUCED (all tested)
catch {forget; destroy}, a pane forgotten and then destroyed, and a notebook tab with a -container frame and an embedded toplevel destroyed in various orders. No X error or crash. (fvogel could not make his own reduced script from the ticket crash either.)
NOT-REPRODUCED (main, 8.6 tip; memory-debug builds)
--enable-symbols=mem for main and for 8.6 tip (out-of-tree, in work-a4/{tclmem,tkmem,tcl86mem,tk86mem}). On each branch I ran place.test alone 15Γ/10Γ and -file [m-p]*.test 3Γ, on Xvfb with no WM. place-14.1 passed every time. The only failures were pack-18.x and place-8.x, which need a WM because they iconify the window; they are unrelated.
-file [m-p]*.test. Proposing to close as works-for-me.
NOT-REPRODUCED (all tested). SCIM itself could not be tested.
echo 'after idle exit' | wish, then a wish that exits on a generated <Control-q>. After that, keys typed into the xterm with an XTEST helper still arrived ("hello" was read). Tested with no XIM and with ibus-daemon --xim (XMODIFIERS=@im=ibus), with 8.6 tip and main. SCIM is not installed. The xscope trace shows SCIM-specific ConvertSelection(@server=SCIM, LOCALES) traffic, so a SCIM server bug is still possible.
NOT-REPRODUCED (main, 8.5)
send_event, which is also used for GENERATED_GRAB_EVENT_MAGIC.
Status now: Pending (Works For Me)
NOT-REPRODUCED (Windows 11, 133% scaling): vista 16x16 against a 17 px scrollbar
Status now: Pending
NOT-REPRODUCED (all tested; per the 2026-09-22 comment, 8.6.18, 9.0.5, 9.1 with Ghostscript); missing attachment manneken.dump
NOT-REPRODUCED (9.1 main, synthetic IME messages only)
NOT-REPRODUCED (9.1 main, 8.6 tip)
update idletasks flushes the drawing because Tk_UpdateObjCmd calls XSync
update idletasks does not flush GDI output.
update idletasks or update plus a 120 ms busy wait, and takes screen shots every 250 ms while Tcl is blocked. Visible squares, idletasks phase: 3 6 8 10 13 15 18 20 (9.1) and 3 5 7 9 11 12 15 17 (8.6). The update phase is the same. Drawing is progressive in both phases, so GdiFlush is not needed.
update idletasks appear one by one, like with update.
NOT-REPRODUCED (9.1 main, 8.6 tip)
foo into the file-name box and presses Open (WM_COMMAND IDOK), with a foo.xyz file present. In the three variants (-defaultextension only, with XYZ filetypes first, with "All files" first), both builds return .../foo.xyz.
NOT-REPRODUCED (all tested)
ttk::frame -borderwidth 5 are placed at 5,5 (main, 8.6, 8.5). jenglish's "known issue" still β¦NOT-REPRODUCED for the original report: children of ttk::frame -borderwidth 5 are placed at 5,5 (main, 8.6, 8.5). jenglish's "known issue" still reproduces: -borderwidth set in a style (ttk::style configure Bordered.TFrame -borderwidth 5) is ignored for the frame's internal margins (child at 0,0). Style -padding is ignored too.
"." -borderwidth 1 from the default and classic themes and inset every ttk::frame by 1px.
NOT-REPRODUCED (all tested)
NOT-REPRODUCED (main)
listbox .l and bind Listbox) prints 9.1.1 bind Listbox: 42. This matches serhiy's 2026-09-19 comment.
Status now: Pending
NOT-REPRODUCED (8.5.19, 8.6.8, 8.6.18, 9.0.5, main)
Status now: Pending
NOT-REPRODUCED (all tested)
-colormap new toplevels). Also ran both scripts under valgrind with the wt main build. No panic and no valgrind errors. The 8.4.11/8.4.2 builds do not work in this environment.
NOT-REPRODUCED (9.1 main)
Status now: Closed (Out of Date)
NOT-REPRODUCED (all tested); CANNOT-TEST with Exceed
Status now: Open
select-tests-private-selection, not merged: Fix [610188], [1719278]: selection tests hang or fail if another client (e.g. a clipboard manager or an X server that syncs the Windows clipboard) requests the NOT-REPRODUCED (all tested); CANNOT-TEST with Exceed
Status now: Pending (Fixed)
NOT-REPRODUCED (main, 9.0, 8.6)
window.test -match window-2.* ran 5 times per version and passed.
Status now: Pending (Out of Date)
NOT-REPRODUCED (9.1 main, 8.6 tip)
.console gets the focus and receives the ButtonPress (clicks=1).
Status now: Closed (Out of Date)
NOT-REPRODUCED (main)
--xim running (XIM_SERVERS=@server=ibus, XMODIFIERS=@im=ibus). All 19 tests pass and nothing hangs. SCIM is not available here.
NOT-REPRODUCED (9.1 main)
open "| tclsh" r+, package require Tk, real XTest click and keys a/b/Return. The child gets the keys and keeps answering over the pipe.
Status now: Pending (Out of Date)
NOT-REPRODUCED (main built with --disable-xft, 8.4.20) β no visible effect on current X.Org servers
-adobe-helvetica-bold-i-normal--17-120-100-100-p-0-iso8859-1). It also lists the real scalable names (--0-0-0-0-p-0-), and all requested sizes resolve correctly.
Status now: Closed (Fixed)
win-nonclient-buttons, in main, 9.0: Fix [1391053]: Win32 nonclient double-click causes spurious Button-1 in apptrunk, in main, 9.0: Fix for 1391053fff: Win32 nonclient double-click causes spurious Button-1 in appcore-9-0-branch, in main, 9.0, 8.6: Fix for 1391053fff: Win32 nonclient double-click causes spurious Button-1 in appcore-8-6-branch, in 8.6: Fix for 1391053fff: Win32 nonclient double-click causes spurious Button-1 in appNOT-REPRODUCED (9.1 main with an 80 ms double-click, 8.6 tip with 300 ms)
Status now: Closed (Fixed)
trunk, in main, 9.0: [1348333] Create many text widgets causes idle event overloadtrunk, in main, 9.0: Backout 4b3b840a41, Because it creates a hang in textWind-17.10. See: [1348333]text-metrics-after-redraw, in main, 9.0: Fix 1348333fff: with many text widgets, the asynchronous line metrics update polled with 1 ms timers while a redisplay was pending, which starved the idle hantext-metrics-after-redraw, in main, 9.0: [1348333] reduce test matrix of mass text widget test as it already takes more than 10 seconds on Ci (1.1 seconds locally)text-metrics-after-redraw, in main, 9.0: textDisp-41.1: back to 30x30 text widgets, which [1348333] needs to show (20x20 passes without the fix), with a font small enough for the toplevel to fit on thetrunk, in main, 9.0, 8.6: [1348333] High number of text widgets block idle queuecore-9-0-branch, in main, 9.0: [1348333] High number of text widgets block idle queuecore-8-6-branch, in 8.6: [1348333] High number of text widgets block idle queuerevised_text, not merged: Merge trunk. The new trunk test textDisp-41.1 becomes textDisp-49.1; [1348333] does not affect the revised widget.text-metrics-idle-wait, in main, 9.0: Merge main. Test textDisp-40.1 renumbered to textDisp-41.1.NOT-REPRODUCED as reported (8.5.19, 8.6 tip, 9.0), but REPRODUCED as a new 9.1 regression (9.1b1/main) with a different cause
update for 900 texts Γ 300 lines takes 1.7 s (9.0: 53 ms). A single text with 100k lines takes 1.26 s to map the first time (9.0/8.6: 4 ms).
bind Text <Map> handler ::tk::TextAutoEnableRtl β ::tk::TextDetectAndTagRtl walks every line in Tcl (split/scan per char) and calls tag remove tk_rtl_right on each line. Every remove invalidates line metrics and restarts the metric timers, and with 900 widgets Tcl_CreateTimerHandler's linear insert takes about 50% of CPU (callgrind). The same full scan also runs from after idle after every tk::TextInsert/paste, i.e. on every keystroke.
[regexp {[\u0590-\u08FF]} [$w get 1.0 end]] finds no RTL char (removing a stale tag if there is one). Otherwise do one tag remove 1.0 end instead of one per line, and clear rtl_detect_pending before the winfo exists check, so the flag no longer stays set when the widget is destroyed before the idle callback runs. Result: 900 widgets 1730β68 ms, 100k-line text 1.26 sβ15 ms. RTL tagging gives the same result as before. textTag.test and text.test pass.
tag remove on every <Map> and after every insert). A fast path is prototyped.
Status now: Closed (Out of Date)
NOT-REPRODUCED (all tested)
tk inactive after reset + 100 ms returns 101β102 on 8.5.19, 8.6 tip and 9.1b1, so tk-6.5 passes
Status now: Closed (Fixed)
NOT-REPRODUCED (9.1, 8.6.18, 8.5.19, 8.4.20). This is consistent with the fix in 8.4.17 (099e9edbef, sticky WS_EX_LAYERED).
Status now: Closed (Out of Date)
NOT-REPRODUCED (all tested). As dgp's Xlib-only leak.c showed, the leak was in the X server, not in Tk.
. configure -cursor watch; . configure -cursor {}, with and without XCURSOR_THEME=Adwaita. Xvfb RSS stayed constant (66028 KB).
NOT-REPRODUCED (9.1 main, 8.6 tip) with synthetic drags
vwait inside them, run a nested event loop inside Windows' modal move/size loop. Something in that nested loop, possibly the mouse capture/timer handling in tkWinPointer.c, ends the move loop early (fvogel saw an unexpected WM_EXITSIZEMOVE), and the window snaps back.
Status now: Closed (Works For Me)
NOT-REPRODUCED (all tested); the original setup (Solaris 8, openwin Xinerama, dtwm) CANNOT-TEST
Status now: Open (Works For Me)
select-tests-private-selection, not merged: Fix [610188], [1719278]: selection tests hang or fail if another client (e.g. a clipboard manager or an X server that syncs the Windows clipboard) requests the NOT-REPRODUCED (all tested)
-constraints failsOnCILinux) on main (wt build) and 8.6 tip, Xvfb with no WM and with icewm. All pass. KDE (the only environment where it hung, most likely a clipboard manager such as Klipper grabbing PRIMARY) not available.
install prefix with spaces: NOT-REPRODUCED (fixed). Source/build directory with spaces: REPRODUCED on main (make fails).
--prefix containing spaces, configure, make and make install all succeed and the installed wish runs; the rpath is quoted correctly. TK_LIB_SPEC in tkConfig.sh is -L/path with space/lib ... unquoted. A source tree under a path with spaces fails in make ("Circular dependency ... sp <- sp", "No rule to make target 'src/unix/../macosx/configure.ac'").
Status now: Open
win-frame-cursor, not merged: Let Windows set the resize cursors on the frame of a toplevel.NOT-REPRODUCED (9.1 main, manual check)
NOT-REPRODUCED (9.1 main, 64-bit, uk-UA locale, en-US input)
the original shrink is NOT-REPRODUCED: with a non-empty menubar (.z) the client area is 400x300. A remaining discrepancy is REPRODUCED (9.1 main, 8.6 tip): a toplevel whose -menu is an empty menu (.x) gets a 400x320 client area (+20 px).
.x (-menu, empty menubar), .y and .z (-menu with a cascade) are all 400x300. The comment's second complaint, a window that grows when wm geometry is repeated with [winfo reqheight .menubar], is NOT-A-BUG. The original .menubar is laid out as a vertical menu and its reqheight grows with every entry; the displayed menubar is the clone .#menubar. Windows repro: win/220865ffff.tcl (prints VERDICT).
winfo reqheight of the menubar's original menu is its vertical-layout height, not the menubar height.
hMenu != NULL && GetMenuItemCount(hMenu) > 0 to AdjustWindowRectEx and retest.
Status now: Closed (Fixed)
trunk, in main, 9.0: Fix for [220791]: Window gives false geometry information; Fix for 6fa2369ec6: X11: under Mutter wm geometry of a zoomed toplevel is offset by the invisible bcore-9-0-branch, in main, 9.0, 8.6: Fix for [220791]: Window gives false geometry information; Fix for 6fa2369ec6: X11: under Mutter wm geometry of a zoomed toplevel is offset by the invisible bcore-8-6-branch, in 8.6: Fix for [220791]: Window gives false geometry information; Fix for 6fa2369ec6: X11: under Mutter wm geometry of a zoomed toplevel is offset by the invisible bx11-gtk-frame-extents, in main: Fix 6fa2369ec6: X11: under Mutter, wm geometry of a toplevel was offset by the invisible borders of its frame after the window manager moved it (zooming, fullNOT-REPRODUCED as reported (the difference is by design; fvwm has a quirk)
wm geometry always returns the requested +120+120 / +130+130. winfo geometry / rootx give the client-area position (e.g. +121+142 under openbox), which is expected: it excludes the decorations. twm would not start here. Under fvwm the first placement is right, but a later wm geometry . +130+130 on the mapped window puts the client (not the frame) at 130,130. The frame is then at 125,107 while wm geometry still says +130+130, which is the ICCCM move/gravity ambiguity on fvwm's side.
wm geometry reports the frame position and winfo geometry the client window, so they differ by the decorations; that is by design. With openbox, and with no WM, both are consistent on 8.4 and 9.1. Suggest closing.