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: Closed (Fixed)
nab-win-appearance-rebuild, in main, 9.0: Reference ticket 354fbe9fe6 in tests winWm-10.5 and 10.6.trunk, in main, 9.0: Fix for 354fbe9fe6: Windows: -appearance set with wm attributes is lost when the wrapper is recreatedREPRODUCED (9.1 main); FIXED on branch nab-win-appearance-rebuild
return TCL_OK for WM_OVERRIDE_APPEARANCE in SynchronizeAppearance.
wm attributes -appearance dark, winfo isdark is 0 after each of wm resizable, wm overrideredirect, -toolwindow, -fullscreen on/off and wm transient (5 of 5); light passes. Side finding: winfo isdark on a window that was never mapped (e.g. a withdrawn .) crashes Tk on Windows: TkpWindowIsDark (win/tkWinWm.c) calls Tk_GetHWND(Tk_WindowId(tkwin)) without creating the window. The repro script now probes a mapped toplevel. Branch nab-win-appearance-rebuild: all 10 checks PASS (BUG NOT PRESENT); winWm.test and wm.test pass (340 tests, 0 failed).
Status now: Open
REPRODUCED (main)
ttk::style configure Row -focusthickness 0; ttk::style map Row -focusthickness {} and a tag with -padding {10 6}, the focused padded row shows a 1px black ring. An unpadded focused row shows none. 9.0 is not affected (its Row layout has no focus element).
-focussolid 1 for Row (the win theme uses a dotted ring, which ignores the thickness entirely). So the focus element always draws a 1px ring. Without padding, the Treeitem.row background inside it paints over the ring. A tag's -padding insets that background (Treeitem.padding) and the ring shows. FocusElementSize already reserves 0 pixels for thickness 0, so the drawing does not match the sizing.
-padding {10 6} and Row -focusthickness 0, checked with a PIL screen grab of the row's top edge. Before: 196 dark pixels. After: 0.
photo -format window)
-focusthickness to 1 when focused, so default rings are still drawn. With thickness 0, the dotted (non-solid) ring is now skipped too, which matches FocusElementSize reserving 0 px.
Status now: Closed (Fixed)
text-bidi-chunk-order, not merged: Fix f5b47c533f (see 59d6d5f6c0): a tag (e.g. the selection) splitting right-to-left text in a text widget made the line scrambled: the font back-end draws atext-bidi-chunk-order, not merged: Fix the insertion cursor at the start of a line of right-to-left text (see 59d6d5f6c0): it was drawn at the left end of the line. ReorderBidiChunks() now alsotrunk, in main, 9.0: Fix cursor insertion bug in RTL text and selection bug in mixed-bidi text 59d6d5f6c0; restore broken RTL text display on Windows; implement ::tk::startOfClustnab-text-mark-stretch, in main, 9.0: Fix text shimmering while a selection is dragged on macOS (see 59d6d5f6c0): since 3403347da9 every mark, the insertion cursor included, ended the base-char text-rtl-highlight, not merged: Text widget: the highlight of a part of a joined right-to-left word (e.g. one Arabic letter selected) did not match its bbox (see 59d6d5f6c0): the chunks of adancing_bidi, in main, 9.0: Merge trunktext*.test files give the same results as trunk. textDisp-37.4 also passes on trunk on macOS. - On trunk and on the branch,…REPRODUCED (main fb166f9f73, X11, bidi). Not applicable to 9.0 and 8.6: they have no bidi layout, so the text stays in left-to-right logical order and the selection does not move.
tag add sel 1.4 1.8, so the text moves. On 9.0.5 and 8.6.18 it stays 3 46 79.
Status now: Closed (Fixed)
trunk, in main, 9.0: Fix for 897f6672f7: Windows: wm deiconify restores a maximized window as normal.core-9-0-branch, in main, 9.0, 8.6: Fix for 897f6672f7: Windows: wm deiconify restores a maximized window as normal.core-8-6-branch, in main, 9.0, 8.6: Fix for 897f6672f7: Windows: wm deiconify restores a maximized window as normal.REPRODUCED (own ticket, filed 2026-10-03); proposed fix in branch win-deiconify-zoomed, not merged
Status now: Closed (Fixed)
x11-withdraw-keep-position, in main, 9.0: Fix 4c5184d974: X11: wm deiconify loses the position of a window moved by the user. A withdrawn window is placed anew by the window manager unless its size hitrunk, in main, 9.0: Fix 4c5184d974: X11: wm deiconify loses the position of a window moved by the usercore-9-0-branch, in main, 9.0, 8.6: Fix 4c5184d974: X11: wm deiconify loses the position of a window moved by the usercore-8-6-branch, in main, 9.0, 8.6: Fix 4c5184d974: X11: wm deiconify loses the position of a window moved by the userREPRODUCED (own ticket, filed 2026-10-03); proposed fix in branch x11-withdraw-keep-position, not merged
Status now: Closed (Fixed)
REPRODUCED (main; 9.0 and 8.6 have no accessibility)
Status now: Closed (Fixed)
REPRODUCED (main; 9.0 and 8.6 have no accessibility)
[unknown] name='Checkbutton', and with 03.patch [check box]. On X11 with a reader running, ttk::checkbutton is aliased to tk::checkbutton (accessibility.tcl), and the class fallback in GetAtkRoleForWidget finds no "Checkbutton" entry either. Also checked:
[dialog].
[%W cget -variable], the variable name, as the value, so every radiobutton starts as checked.
Status now: Closed (Wont Fix)
REPRODUCED (main; 9.0 and 8.6 have no accessibility)
wm geometry . 360x240 the extra "Open" button is not mapped under Xvfb's default fonts (winfo ismapped 0), so the output wrongly shows the name preserved. With 360x400 it gives exactly the reported "after map: name=Button / description=Open".
.b*, .c[x]).
bind all <Destroy> {+...}. An application's bind all <Destroy> without "+" silently removes the cleanup. generic/tkAccessibility.c already has a C WindowDestroyHandler that frees the attribute table, and this bookkeeping could live there.
-takefocus 1 in _init stays (see 595d72d0a6).
bind all <Destroy>.
Status now: Closed (Fixed)
REPRODUCED (main; 9.0 and 8.6 have no accessibility)
windowingsystem ne "x11" guard covers only 10 of the 15 help bindings. TScrollbar, Menubutton, TMenubutton, TNotebook and Text still set help on X11, which with item 2 becomes the ATK description that Orca reads on focus.
Status now: Closed (Fixed)
REPRODUCED (main; 9.0 and 8.6 have no accessibility)
exec spd-say synchronously from the event loop. That also blocks the AT-SPI bus, which Tk serves from the same loop: during the blocking tour, Orca's queries timed out and it processed the events seconds late.
exec spd-say -- $text ... & with the espeak fallback (dropping the useless quote escaping; "--" protects texts starting with "-"), and _handle_keypress no longer speaks on X11. Word, focus and state speech and the per-call check are left as they are.
exec ... &) at least stops the event loop, and with it the AT-SPI replies, from blocking.
Status now: Closed (Wont Fix)
REPRODUCED (main; 9.0 and 8.6 have no accessibility)
.f.save .f.name .f.enable .f.status; without a reader .f.save .f.name .f.enable. The label's -takefocus becomes 1 after map.
$w configure -takefocus 1 for every widget it initialises, including Label/TLabel. unix/tkUnixAccessibility.c:tk_text_get_text()/tk_text_get_character_count() are stubs, so a reader's review commands get no text for static widgets. (The ATK state set already omits FOCUSABLE for labels, which matches leaving them out of the Tab order.)
Status now: Closed (Fixed)
trunk, in main, 9.0: Fix 3f1ad1ff50: Windows: pointer warp could land one pixel short of the requested positioncore-9-0-branch, in main, 9.0, 8.6: Fix 3f1ad1ff50: Windows: pointer warp could land one pixel short of the requested position. Don't bother reserving a stub entry for TkpChangeFocus2core-8-6-branch, in main, 9.0, 8.6: Fix 3f1ad1ff50: Windows: pointer warp could land one pixel short of the requested positionREPRODUCED (own ticket, filed 2026-10-02); proposed fix in branch win-warp-rounding, not merged
Status now: Open
trunk, in main, 9.0: Selected fix from deca13e833: correct state left by tests: pack-20.6 did not restore "pack propagate ."; event.test leaves the pointer over the larger windowscore-9-0-branch, in main, 9.0: Selected fix from deca13e833: correct state left by tests: pack-20.6 did not restore "pack propagate ."; event.test leaves the pointer over the larger windowstrunk, in main, 9.0: Selected fix from deca13e833: test bind-34.1: fit a 800x600 screencore-9-0-branch, in main, 9.0: Selected fix from deca13e833: test bind-34.1: fit a 800x600 screentrunk, in main, 9.0: Fix deca13e833: Tests fail at high display scale (tests did not take into account the minimum width of a toplevel).core-9-0-branch, in main, 9.0, 8.6: Fix deca13e833: Tests fail at high display scale (tests did not take into account the minimum width of a toplevel).core-8-6-branch, in 8.6: Fix deca13e833: Tests fail at high display scale (tests did not take into account the minimum width of a toplevel).tests-min-width, in main: Test textDisp-33.3 failed on Windows when the 480 pixel wide frame .f and the 80-column text widget were wider than the screen: the text widget was laid out a stests-high-dpi, not merged: Test font-10.9: use TkFixedFont on Windows.REPRODUCED (own ticket, filed 2026-10-02); proposed fix in branch tests-high-dpi, not merged
Status now: Open
REPRODUCED (own ticket, filed 2026-10-02); no fix: branch aqua-bounded-idle-loops was closed as unwanted (it would mask the issue)
Status now: Closed (Fixed)
trunk, in main, 9.0: Fix d08538fd78: Regression in 9.1: wrapped text counts spaces at end of line, splits words, breaks after leading spaces (X11 with bidi, Windows)REPRODUCED (own ticket, filed 2026-10-01); proposed fix in branch shaping-whole-words, not merged
Status now: Closed (Fixed)
trunk, in main, 9.0: Fix for d1a711b500: X11: wm geometry reports the requested position after the window manager moved the window out of a panel's areacore-9-0-branch, in main, 9.0, 8.6: Fix for d1a711b500: X11: wm geometry reports the requested position after the window manager moved the window out of a panel's areacore-8-6-branch, in 8.6: Fix for d1a711b500: X11: wm geometry reports the requested position after the window manager moved the window out of a panel's areaREPRODUCED (own ticket, filed 2026-09-30); proposed fix in branch x11-wm-position-work-area, not merged
Status now: Closed (Fixed)
REPRODUCED (own ticket, filed 2026-09-30); proposed fix in branch menu-cascade-flip, not merged
Status now: Closed (Fixed)
x11-bidi-font-reconfigure-leak, in main, 9.0: Fix e8d4c8a577: X11 (HarfBuzz/SheenBidi font backend): [font configure] of a font in use leaks the old font. TkpGetFontFromAttributes re-initialized a font intrunk, in main, 9.0: Fix e8d4c8a577: X11 (HarfBuzz/SheenBidi font backend): [font configure] of a font in use leaks the old fontREPRODUCED (main 40.3 KB per font change; 9.0.5 and 8.6.18 0.0 KB, they use tkUnixRFont.c)
font configure of a named font used by a label) under Xvfb :101 with build-trunk, tk9.0 and tk8.6. With the prototype: 0.0 KB per change. valgrind on the patched build (150 changes): no invalid reads or writes, 512 bytes "definitely lost" not from the font code. font.test, unixFont.test and fontchooser.test pass (same counts as unpatched main).
fontPtr->font.fid != 0 to mean "re-used record". A new font that fails after XLoadFont() is therefore never freed. Once FinishedWithFont() is added, a re-used record that fails is left with dangling faces/pattern/fontset pointers, and TkpDeleteFont() would free them a second time.
reused flag, and drops the double XftPatternDestroy(). Font tests pass and the reproducer is flat.
Status now: Closed (Fixed)
REPRODUCED (own ticket, filed 2026-09-29); proposed fix in branch x11-shaper-long-string, not merged
Status now: Closed (Fixed)
embed-container-destroyed, in main, 9.0: Fix 4a25f316f7: an embedded application exited with BadDrawable when its container was destroyed while it had pending drawing. ErrorProc() now ignores BadDrawembed-container-destroyed, in main, 9.0: Fix 5f7ba8c5a3: Restore the fix for 4a25f316f7, which was backed out because the table of deleted windows grew in loops which created and destroyed windows trunk, in main, 9.0, 8.6: Fix 5f7ba8c5a3: Restore the fix for 4a25f316f7core-9-0-branch, in main, 9.0: Fix 5f7ba8c5a3: Restore the fix for 4a25f316f7core-8-6-branch, in main, 9.0, 8.6: Fix 5f7ba8c5a3: Restore the fix for 4a25f316f7REPRODUCED (own ticket, filed 2026-09-26); proposed fix in branch embed-container-destroyed, not merged
Status now: Closed (Fixed)
canvas-default-error-crash, in main, 9.0: Fix 434c8dd804: crash in Tk_ConfigureWidget when a default value of a canvas item option is invalid. The error message used specPtr->dbName, which is NULL fortrunk, in main, 9.0: Fix 434c8dd804: crash in Tk_ConfigureWidget when a default value of a canvas item option is invalidcore-9-0-branch, in main, 9.0, 8.6: Fix 434c8dd804: crash in Tk_ConfigureWidget when a default value of a canvas item option is invalidcore-8-6-branch, in main, 9.0, 8.6: Fix 434c8dd804: crash in Tk_ConfigureWidget when a default value of a canvas item option is invalidREPRODUCED (own ticket, filed 2026-09-25); proposed fix in branch canvas-default-error-crash, not merged
Status now: Closed (Fixed)
atk-util-get-root, not merged: Fix b9d85fc100: X11 accessibility: root accessible is not registered with ATK. Tk defined its own global atk_get_root(), relying on symbol interposition to ovREPRODUCED (own ticket, filed 2026-09-25); proposed fix in branch atk-util-get-root, not merged
Status now: Closed (Fixed)
configure-bidi-without-harfbuzz, in main, 9.0: Fix 1dfc71ae4a: configure fails without HarfBuzz although --enable-bidi was not given. Unless --enable-bidi is given explicitly, a missing, too old or unusablconfigure-bidi-requires-xft, in main, 9.0: Bidi requires Xft: disable it if Xft is disabled or not found 1dfc71ae4atrunk, in main, 9.0: Fix 1dfc71ae4a: configure fails without HarfBuzz although --enable-bidi was not givenconfigure-bidi-requires-xft, in main, 9.0: Merge trunkREPRODUCED (own ticket, filed 2026-09-25); proposed fix in branch configure-bidi-requires-xft, configure-bidi-without-harfbuzz, not merged
Status now: Open
REPRODUCED (own ticket, filed 2026-09-24); no fix yet
::tk::accessible::speak command backed by global speechd state (spd_conn, pending message, Tcl timer). The thread check now lives in TkAtkAccessibility_Init before that call. Non-ATK threads also get a no-op ::tk::accessible::speak, because the speechd state is process-wide too. As a result, SpeechExitProc is registered only once.
load libtcl9tk9.1.so Tk, then create, pack and destroy 50 frames, then destroy ..
--disable-accessibility build of the same main crashes 3/40 at 8 threads ("malloc(): unaligned tcache chunk detected"). That bug is separate and not addressed here.
speak no-op). Backup: 97a7ddac25-atk-thread.patch.1024.
Status now: Closed (Fixed)
photo-transparency-set-alpha, in main, 9.0: Fix 54c2ca0e94: photo: pixels made semi-transparent with "transparency set ... -alpha" are drawn opaque.photo-transparency-set-alpha, in main, 9.0: Rebase to mainREPRODUCED (own ticket, filed 2026-09-24); proposed fix in branch photo-transparency-set-alpha, not merged
Status now: Closed (Fixed)
text-rtl-detect-speed, in main, 9.0: Speed up the RTL auto-detection of the text widget and fix its per-widget state.text-rtl-detect-speed, in main, 9.0: Add tests textTag-19.5 to 19.7 for all RTL character ranges, characters outside them, and punctuation and whitespace in RTL lines 5d983ebf48.text-rtl-detection, in main, 9.0: Fix 5d983ebf48 and 3d6de81648: speed up the RTL auto-detection of the text widget and fix its per-widget state. Combines branches text-rtl-detect-speed and trunk, in main, 9.0: Fix 5d983ebf48 and 3d6de81648: speed up the RTL auto-detection of the text widget and keep its pending state per widget. Merge text-rtl-detection (Serhiy Stnab-text-rtl-scan, in main, 9.0: Text RTL detection: one regexp search of the text instead of a Tcl loop on every line at each keystroke; tag changed only where needed.text-rtl-detection, in main, 9.0: Merge trunkREPRODUCED (own ticket, filed 2026-09-24); proposed fix in branch text-rtl-detect-speed, not merged
Status now: Closed (Fixed)
bug-56d4d132fd-child-interp, in main, 9.0: Merge trunkREPRODUCED (main). Fix on branch bug-56d4d132fd-child-interp (db2fc66a5f and its follow-ups by kjnash, including the review changes), not merged.
interp create foo; foo eval package require tk did not fail outright. Instead it found main/lib/tk9.1/pkgIndex.tcl through auto_path and loaded a second, shared libtcl9tk9.1.so into the process (info loaded in the child shows both {} Tk and the .so), so the child silently uses a different Tk build. Shared builds of main and 9.0 work.
load {} Tk for static builds.
Status now: Closed (Fixed)
x11-coords-to-window, in main: Fix 586f722cdd and 220856ffff in Tk_CoordsToWindow() on X11. A toplevel that was just withdrawn was still found while the window manager had not yet unmappetrunk, in main, 9.0: Fix for 586f722cdd: New test winfo-4.8 failscore-9-0-branch, in 9.0, 8.6: Fix for 586f722cdd: New test winfo-4.8 failscore-8-6-branch, in 8.6: Fix for 586f722cdd: New test winfo-4.8 failsREPRODUCED (main, 9.0, 8.6) as a timing race. winfo-4.8 itself passes here with no WM and with twm/fvwm/icewm/openbox/wmaker/i3/xfwm4, but it fails whenever the WM is slower than after 10.
winfo containing right after wm withdraw .one; update. It returns .one on 9.0+fvwm, main/9.0+icewm, and main/9.0/8.6+openbox. After 10 ms it returns "", and winfo ismapped .one is already 0.
wmPtr->reparent) stays mapped until the WM handles the UnmapNotify. XTranslateCoordinates still finds the frame, and the code accepts that toplevel without checking whether it is mapped.
gotToplevel it returns NULL if !Tk_IsMapped(winPtr). It adds test winfo-4.9, which uses no delay after the withdraw. winfo-4.9 fails without the fix under openbox/icewm and passes with it. winfo.test has no new failures: with no WM, winfo-9.4/9.7 fail both before and after the patch; under wmaker, winfo-4.5 fails both before and after.
wm withdraw the WM frame stays mapped until the WM reacts, and Tk_CoordsToWindow accepts the frame without checking that the toplevel is mapped. A fix and a test that doesn't depend on timing (winfo-4.9) are ready.
REPRODUCED (9.1 main); NOT-REPRODUCED (8.6 tip)
-angle 90, with bbox rectangles).
fontType & RASTER_FONTTYPE, so the fallback picks a TrueType font. Alternatively, create angled fonts with OUT_TT_ONLY_PRECIS.
9.1: font actual gives Courier, and the text is drawn unrotated (ink 53x10). Courier New, Times and Helvetica are rotated.
8.6: Courier resolves to Courier New and is rotated.
{Courier New}. Verified: the Courier text is now rotated, and font.test, winFont.test and canvText.test pass (0 failures). Before the test change, winfont-2.8 failed as expected.
ABCDEFGH in {Courier 12} at -angle 90 must be taller than twice its width; fails before: yes; passes after: yes). The relaxed winfont-2.8 in the patch passes either way.
REPRODUCED (main, 8.6, 8.4). This is long-standing behaviour.
-width 3 -height 1 -bd 4 -relief flat -padx 6 -pady 6 and 3-line text. The glyphs fill the whole 56x40 window, including the padding and the border.
Status now: Closed (Fixed)
win-menubar-colors-ownerdraw, not merged: Fix 11bd4a03a0: the Windows menu bar ignored the colors and fonts of the menu. The items of a menu bar with non-default colors or fonts are now drawn by Tk (owin-menubar-colors-uah, in main, 9.0: Fix 11bd4a03a0: the Windows menu bar ignored the colors and fonts of the menu. A menu bar with non-default colors or fonts is now drawn by Tk, handling the unwin-menubar-colors-ownerdraw, not merged: The default font of the menu is the system menu font specified by its name and size, not TkMenuFont: do not draw a menu bar with the default font by Tk.win-menubar-colors-uah, in main, 9.0: Merge mainREPRODUCED (9.1 main, 8.6 tip), limitation / RFE
.#m gets -bg black and the font, so X11 honors them. Windows repro script: win/11bd4a03a0.tcl (interactive; press a button to record the verdict).
MF_STRING (only other menus use MF_OWNERDRAW). DrawMenuEntry* returns early for MENUBAR, and there is no SetMenuInfo(hbrBack). So Windows draws the bar with system colors and fonts. A fix needs owner-drawn or UAH-custom-drawn menubar items, as in the links in the ticket.
-bg red -fg yellow -font {Courier 24 bold}, captured with CopyFromScreen, has 0 red and 0 yellow pixels on 9.1 and 8.6: system font, default colors.
Status now: Closed (Fixed)
trunk, in main, 9.0: 9ab6e37e1a disallow "wm forget ."core-9-0-branch, in main, 9.0: 9ab6e37e1a disallow "wm forget ."wayland, not merged: Fix wm-forget-3: on Wayland, wm forget . forgot the main window instead of raising an error, as on other platforms (bug 9ab6e37e1a).REPRODUCED (main fb166f9f73, 9.0.5, 8.6.18: "wm forget .; pack ." → SIGSEGV)
REPRODUCED (main, 9.1, 9.0; confirmed by reading the code; 8.6 and 8.7 do not have this code)
bool (*)(Tcl_Obj *), but Tcl (tclmain and tclDecls.h) declares int Tcl_IsEmpty(Tcl_Obj *). 9.0 has the same cast.
#define Tcl_IsEmpty above TkObjIsEmpty (from 50a8805c).
int (*)(Tcl_Obj *) and return Tcl_IsEmpty(objPtr) != 0;. It builds warning-free, and config.test passes: 241 passed, 1 skipped. I did not rerun UBSan.) If TIP #748 changes the Tcl return type to bool, the cast must follow it.
int prototype. That is a two-line change, which I can commit to 9.0 and main.
int Tcl_IsEmpty(Tcl_Obj *), and tkConfig.c still casts the stub slot to bool (*)(Tcl_Obj *). After the patch the cast matches. It builds without warnings.
-fsanitize=function, which needs Tcl itself built with clang UBSan.
Status now: Closed (Fixed)
configure-cups-cflags, in main, 9.0: Fix 3ac12ff34c: configure may not find cups.h. Add the output of "cups-config --cflags" to CUPS_CFLAGS, so cups.h is found in a non-default prefix, e.g. /usr/trunk, in main, 9.0: Fix 3ac12ff34c: configure may not find cups.hcore-9-0-branch, in main, 9.0: Fix 3ac12ff34c: configure may not find cups.hcups-config --cflags added to CUPS_CFLAGS, cups.h is found and Tk links with libcups. Proposed fix in branch configure-cups-cflags. The OpenBSD port applies the same patch.REPRODUCED (main, 9.0; 8.6 has no CUPS code)
cups-config whose --cflags returns -I<dir>, with cups/cups.h only in that dir. Unpatched main configure prints "checking for cups/cups.h... no" and leaves CUPS_CFLAGS empty. Patched configure prints "yes" and sets CUPS_CFLAGS = -DHAVE_CUPS -I<dir>. (Real libcups-dev is not installed here.)
cups-config --cflags, so AC_CHECK_HEADER and the build of tkUnixPrint.c miss non-default include dirs, e.g. /usr/local/include on BSD.
cups-config --cflags, so cups.h in a non-default prefix is not found. The fix is to append it as suggested, for 9.0 and main.
Status now: Closed (Fixed)
demo-colors-dark-mode, in main, 9.0: Fix for 042da6013e: give the demos colours which go with their background.trunk, in main, 9.0: Fix for 042da6013e: Pendulum demo text not visible under dark modecore-9-0-branch, in main, 9.0, 8.6: Fix for 042da6013e: Pendulum demo text not visible under dark modecore-8-6-branch, in 8.6: Fix for 042da6013e: Pendulum demo text not visible under dark modedemo-colors-dark-mode 72d8eb4751: the three text items get a fill of their own, so they no longer depend on a default foreground which a dark appearance inverts. This is the conservative half of the question Jan raised: the white background stays, which is what the phase space graph needs for the reason Christopher gave, and only the items which had no colour of their own are given one. …REPRODUCED by code reading (main and 8.6): on Aqua, DEF_CANVITEM_OUTLINE is NORMAL_FG = systemTextColor, which is white in dark mode, while the canvases have -background white. Not tested on macOS.
-fill black
-fill black, about 6 lines; applies to main; the same change is needed on 8.6, whose text lines differ slightly)
Click to Adjust..., θ, δθ) have fill=black and valid coordinates. On X11 the default text fill is already black, so there is no visible change.
Notes:
diff-command = gdiff-command, so a plain fossil diff > file fails. I used fossil diff -i.
Status now: Closed (Fixed)
unix-tcl-installed-headers, in main, 9.0: Fix b900dc7552: compilation using installed Tcl fails if Tcl source is not accessible.win-tcl-installed-headers, in main, 9.0: Fix b900dc7552 for MinGW: compilation using installed Tcl fails if Tcl source is not accessible.trunk, in main, 9.0: Fix b900dc7552: compilation using installed Tcl fails if Tcl source is not accessible.core-9-0-branch, in main, 9.0: Fix b900dc7552: compilation using installed Tcl fails if Tcl source is not accessible.core-8-6-branch, in main, 9.0, 8.6: Fix b900dc7552: compilation using installed Tcl fails if Tcl source is not accessible.trunk, in main, 9.0: Fix b900dc7552 for MinGW: compilation using installed Tcl fails if Tcl source is not accessiblecore-9-0-branch, in main, 9.0: Fix b900dc7552 for MinGW: compilation using installed Tcl fails if Tcl source is not accessibleREPRODUCED (main; 8.6 has the same Makefile.in). With TCL_SRC_DIR pointing to a directory that is not readable, cc1 fails with "Permission denied" on -I$TCL_SRC_DIR/generic. When the directory does not exist, the build finds tcl.h only if the headers are on a default or CPATH include path, because Tk never uses TCL_INCLUDE_SPEC.
-I${TCL_GENERIC_DIR} -I${TCL_PLATFORM_DIR} (from TCL_SRC_DIR) unconditionally and ignores TCL_INCLUDE_SPEC.
$TCL_SRC_DIR/generic/tcl.h is readable, and to TCL_INCLUDE_SPEC otherwise. Verified: a full build succeeds with the unreadable source directory, and a build against tclmain/unix still uses the source tree.
REPRODUCED (main, 9.0, 8.6, 8.5) on X11. Marc's "correct" output was from macOS mac_send only.
update after tk appname foo.
{t_s_dup #2} {t_s_dup {t_s_dup #2}} t_s_dup (4 of 4 runs)
REPRODUCED (9.1 main). The crash is GDI handle exhaustion.
Tk_GetPixmap() returning None, which win/tkWinPixmap.c does when CreateBitmap and CreateDIBSection both fail. TkPutImage() then gets drawable 0, which is a NULL TkWinDrawable in TkWinGetDrawableDC(). A fix would return None from XCreateBitmapFromData() when pix == None, and make GetBitmap() (tkBitmap.c) fail with an error instead of caching a None bitmap. Graceful degradation only: running out of GDI handles is an OS limit.
tcltest target in tcl91 and tcl8.6; only new build outputs were added) and used testthread (work-win/a58tt.tcl + a58.cmd). With the ref91 build, 50–500 threads were OK. 600 threads crashed with 0xC0000005 in TkWinGetDrawableDC(NULL): the per-process GDI count reached its 10000 limit.
After fixing that NULL case, a second crash appeared: 0xC0000094 (integer divide by zero) in Tk_GetPixmap. A thread whose TkpOpenDisplay found GetDC(NULL) failing got planes=0 and depth=0 in TkWinDisplayChanged.
With the prototype, 600, 800 and 1000 threads run without a crash. The extra threads get the Tcl error couldn't connect to display ":0" (721 of 1000).
cannot create bitmap "gray25" (errorCode TK BITMAP CREATE).
Verified on 9.1: bitmap, button, canvas, entry, font, frame, imgPhoto, imgBmap, image and listbox tests all pass (0 failures).
REPRODUCED (main, 9.0); not in 8.6, 8.5 or 8.7b1 (no ICU word procs there)
Status now: Closed (Fixed)
named-font-late-creation, in main, 9.0: Fix c81e0ccee2: a named font was not used by widgets that referred to its name before it was created. Fonts cached under the name are now converted to the newtrunk, in main, 9.0: Fix for c81e0ccee2: Named font late creationcore-9-0-branch, in main, 9.0, 8.6: Fix for c81e0ccee2: Named font late creationcore-8-6-branch, in 8.6: Fix for c81e0ccee2: Named font late creationnamed-font-late-creation, in main, 9.0: Rebase to mainREPRODUCED (main, 9.0, 8.6, 8.5)
-font F2 stays at the fallback size after font create F2 -size 40 (reqwidth 55 instead of 192). The ttk::style case is the same. The fix from branch bug-c81e0cce-named-font-late-creation (ed0d5d2335/560de1252d, based on 8.6) was never merged.
REPRODUCED (main, 8.6). This is largely inherent to X11 clipboard managers.
clipboard append aa followed by clipboard clear, both xsel -b and Tk's own clipboard get still return "aa"; a later append ("bb") is seen correctly. Without a manager, another client that asks for STRING after clipboard clear gets "CLIPBOARD selection doesn't exist or form STRING not defined".
clipboard clear to serve an empty STRING/UTF8_STRING, but real xclipboard may still ignore zero-length data (could not verify; xclipboard not installed).
clipboard clear, Tk owns CLIPBOARD with no targets, so the manager's fetch fails and it re-asserts the old content. X11 has no way to say "the clipboard is empty", so this looks like a limitation of the protocol rather than a Tk bug.
Status now: Closed (Fixed)
ttk-progressbar-stopped-animation, in main, 9.0: Fix 89436bd244: stopped indeterminate ttk::progressbar redraws continuously.trunk, in main, 9.0: Fix 89436bd244: Stop indeterminate ttk::progressbar redraws continuouslycore-9-0-branch, in main, 9.0: Fix 89436bd244: Stop indeterminate ttk::progressbar redraws continuouslyREPRODUCED (main, 9.0). Regression from check-in ea571a1307 (2025-03-06, the fix for ef1bfef57e). 8.6 is not affected.
-period 10 (as aquaTheme.tcl sets -period 100), a stopped indeterminate bar with -value 0 keeps incrementing -phase and redrawing on main. Windows themes set no -period, which matches fvogel's observation.
period > 0 && mode == indeterminate. ea571a1307 dropped the value > 0.0 condition, so every indeterminate bar on Aqua redraws 10 times per second even when it has not been started ([$pb stop] sets -value 0).
value > 0.0 in AnimationEnabled and removes the unused maximum. The test fails on unpatched main and passes with the patch; progressbar.test 21/21.
value > 0 check in AnimationEnabled. Now any indeterminate progressbar animates on Aqua (period 100) even when stopped. A fix restoring the check is ready, with a test.
Status now: Closed (Fixed)
panedwindow-sash-keep-request, in main, 9.0: Fix 7c51624a96: moving a sash in a panedwindow stretched by the user made it request its current size, so a gridded toplevel (e.g. with text -setgrid 1 panes)REPRODUCED (main, 8.6). The grid bookkeeping breaks; I did not see the pixel blow-up (0 or 32483 px) on X11.
text -setgrid 1 panes. The toplevel was resized from outside with XResizeWindow on the wrapper, then the sash was moved with sash place or a B1 drag.
After the resize, every sash move makes the reported grid geometry wrong: at 350 px, wm geometry goes from 26x11 to 15x11; later, 4x11 at 329 px. The toplevel keeps its pixel size here because openbox/icewm don't re-apply the changed hints. The WMs on Aqua/Win evidently do (Marc's report).
Without -setgrid everything stays consistent. Main's widget demo no longer uses -setgrid: 0e800a5026 (main) and cafa154041 (9.0), 2025-03-20/21. So the demo itself no longer shows the bug.
Status now: Closed (Fixed)
x11-render-before-xft, in main: Fix b298b92ba7: when Tk was loaded into one thread after another on X11, a later thread died with a random X error. Xft's close-display hook frees glyphs throtrunk, in main, 9.0: Fix for b298b92ba7: Possible Tk regression when loading into threadscore-9-0-branch, in 9.0, 8.6: Fix for b298b92ba7: Possible Tk regression when loading into threadscore-8-6-branch, in 8.6: Fix for b298b92ba7: Possible Tk regression when loading into threadsxft-link-xrender, in 9.0: Fix 09ee8c51fe: static build failed with undefined reference to XRenderQueryExtension. tkUnixEvent.c calls it since b298b92ba7 was fixed, but -lXrender was xft-link-xrender-86, in 8.6: Fix 09ee8c51fe: static build failed with undefined reference to XRenderQueryExtension. tkUnixEvent.c calls it since b298b92ba7 was fixed, but -lXrender was REPRODUCED (main, 9.1b1, 9.0.5, 8.7b1, 8.6 tip, 8.6.13, 8.6.9)
thread::create {package require Tk; ...} + thread::release, without a WM.
With the reporter's exact script, 9.0.5 and 8.7b1 fail but main, 9.1b1 and 8.6 pass. Bisect says main started passing at ea378fca79 (2026-05-28, TIP 740 merge), but that only moved the first Xft call out of the init path.
Once each thread creates a widget with a font (pack [label .l -text hi]; update), every version fails within 3–5 iterations with a random X error ("BadRequest", "BadLength") and the process exits. This happens even when each thread has fully exited before the next one starts, so it is not a thread race.
Close hooks run in LIFO order. Workaround in unix/tkUnixEvent.c TkpOpenDisplay: call XRenderQueryExtension() right after opening the display, so RENDER is registered before Xft and its hook runs last.
Separate issue: the process often segfaults at exit (rc 139) in every version, including 8.6, if threads with Tk were released just before. Not investigated.
Status now: Closed (Fixed)
text-basechunk-threads, in main, 9.0: Make the base chunk of the text layout thread-specific.trunk, in main, 9.0: Fix a0c1a9c6c6: Make the base chunk of the text layout thread-specificcore-9-0-branch, in main, 9.0, 8.6: Fix a0c1a9c6c6: Make the base chunk of the text layout thread-specificcore-8-6-branch, in main, 9.0, 8.6: Fix a0c1a9c6c6: Make the base chunk of the text layout thread-specificREPRODUCED (main on X11). 8.6 and 9.0 on X11 don't build with base chunks and are not affected there; Windows/macOS 8.6/9.0 are affected per the code.
Note: in main, unix/tkUnixInt.h defines TK_LAYOUT_WITH_BASE_CHUNKS as 0 when there is no bidi. tkTextDisp.c only tests #ifdef, so base chunks are enabled even with --disable-bidi.
static TkTextDispChunk *baseCharChunkPtr (marked "TODO: Thread safety"). Concurrent layouts in different threads overwrite it.
grid info and place info return "" but pack info raises "window ".f" isn't packed". Beh…Status now: Closed (Fixed)
bug-3f5867c997, in main, 9.0: Fix 3f5867c997: Inconsistency between grid info, place info and pack infotrunk, in main, 9.0: Fix for 3f5867c997: Inconsistency between grid info, place info and pack infoREPRODUCED (main, 8.6, 8.4): for an unmanaged window, grid info and place info return "" but pack info raises "window ".f" isn't packed". Behaviour has always been this way and is enforced by tests pack-17.2 and grid-5.4.
pack info return "" is a small change, but scripts may catch it to test whether a window is packed. That needs a decision (TIP/changes note) rather than a bug fix. Cheap alternative: document the current behaviour in pack.n, grid.n and place.n.
pack info to return an empty list is a small change but visible to scripts. I suggest either a TIP-level decision for 9.1 or documenting the current behaviour in the man pages.
-format gif still fails with "too many colors". This is really an RFE.REPRODUCED (main, 8.6). Writing a photo with 1024 colors using -format gif still fails with "too many colors". This is really an RFE.
REPRODUCED (main, 8.6)
REPRODUCED (9.1 main, 8.6 tip)
9.1: the process aborts (0x80000003 = Tcl_Panic; nothing on stderr).
8.6: the panic dialog "Fatal Error: Fail to allocate bitmap" appears (win/tkWinDraw.c:TkPutImage, a panic that main no longer has).
With the prototype, 9.1 creates all 12000 images and exits 0: images beyond the quota are simply not displayed. work-win/bmerr.tcl: after 12000 photo labels, label -bitmap gray25 gives the Tcl error "cannot create bitmap", and a new toplevel+button+update does not crash.
image create/-image is not possible without an API change, because Tk_GetImage has no error path from getProc.
Not changed: Tk_GetPixmap still tries a one-time MessageBox ("Error from CreateDIBSection"). I never saw it appear, probably because MessageBox itself needs GDI objects. It could be removed.
REPRODUCED (main, 8.6; the same code goes back to 8.4)
When the view is scrolled, the old behaviour is kept, so glyphs scrolled out of view do not bleed into the padding. Verified: the cursor at 1.0 is 4 px wide and is erased when the cursor moves. The textDisp, text, textTag and textIndex tests pass (1438 passed, 0 failed).
Status now: Closed (Fixed)
trunk, in main, 9.0: Implements line breaks (UAX #14) and word/sentence breaks (UAX #29) for Unicode extended grapheme clusters utilizing the mojibake Unicode library, and implementREPRODUCED (main, 9.0, 8.6); really an RFE (dictionary-based line breaking)
...รบ้านก|ารบ้าน... (KO KAI | SARA AA). Combining marks do stay with their base. At -width 6 the lines break correctly only because the word happens to be 6 glyphs wide. Main's HarfBuzz/SheenBidi shaping does not change where lines break.
REPRODUCED (main, 9.0); 8.6 and 8.7 (no ICU) behave the old way
Ctrl-Right |set |::var1 |value!!|!!! / |set |::var2 |"$value |+ |$value2"
Ctrl-Left |set |::|var1 |value|!!|!!|! / |set |::|var2 |"$|value |+ $|value2|"
!!!!! and :: therefore produce unpredictable stops, and the TextNextWord (endOfWord then startOfNextWord) and TextPrevPos steps pair up inconsistently. Since b4a14597, Ctrl+Right goes to the start of the next word on every platform.
!!|!!|!, $|value). Using the ICU rule status to group punctuation runs would give the consistent stops editors have.
!, : or $ counts as its own word. The single extra icu_next()/icu_previous() step then lands in the middle of a punctuation run (value!!|!!!, value!|!!|!!, :|=, y-|>z).
ubrk_getRuleStatus, a newly loaded symbol) and does not end in a space, and the character after it (surrogate pairs decoded) is neither a space nor Tcl_UniCharIsWordChar. A run of punctuation then counts as one word. Checking the rule status, and not only the characters, keeps the boundary after a letter plus a combining mark. If the symbol is missing, the old behaviour is kept. The ICU used is the system libicuuc.so.78, loaded at run time by Icu_Init; the normal --disable-bidi build already loads it (::tk::startOfNextWord is the C command, and cluster.test's needsICU constraint is true). The text widget's default -locale C goes through ICU; -locale tcl8 still uses the Tcl 8 procs and is unchanged (|set ::|var1 |value!!!!! before and after). 168f3ef130.patch (54 changed lines, 42 C + 12 test)
event generate <Control-Right>/<Control-Left> on the build in wt-a1.
Before: R set |::var1 |value!!|!!!|, L |set |::|var1 |value!|!!|!!; R x |:= |y->|z|, L |x :|= |y-|>z.
After: R set |::var1 |value!!!!!|, L |set |::|var1 |value|!!!!!; R x |:= |y->z|, L |x |:= y|->z.
The second ticket line ("$value + $value2") is unchanged and was already coherent.
ab!!!cd ::ef, constraint needsICU) (fails before: yes, all 3; passes after: yes)
startOfPreviousWord $text end, and end is the last character, not the cursor position. Ctrl+Left therefore skips a one-character word right before the cursor ("a b c": from the end it goes to b, in 8.6.18 too; + $|value2 misses the stop before $).
next() when the boundary is followed by non-space, so endOfWord("ab!!!cd",0) is 5 (was 3). Ctrl+Right (endOfWord + startOfNextWord, from b4a14597) thus still stops only after whitespace, now consistently.
ubrk_getRuleStatus resolves there (it is exported by the system icu.dll), then run cluster.test (needsICU must be true) and text.test/entry.test, and try the ticket snippet with Ctrl+Left/Right.
!!!!! or -> is one word for Ctrl+Left/Right, as in editors. With -locale tcl8 the 8.6 behaviour is still available.
REPRODUCED (main, 9.0, 8.6, 8.6.8, 8.5)
focus .e1; focus .e2 (comV1 calls update; comV2 sets ::v1) leaves .e1 state = invalid on all versions listed
validate), where there is no edit to reject. The man page says this rejection applies only "during prevalidation". The update in comV1 runs e2's focus validation, which sets ::v1 while e1 is still VALIDATING.
validate), the entry is marked invalid even though -validatecommand returned true. The documented "edit is rejected" rule should only apply to prevalidation. Prototype fix limits it to insert/delete validation.
0 newdata invalid. After: 1 newdata {}.
REPRODUCED (main, 8.6)
wm attributes . -zoomed 1, then toggling . configure -menu 4 times. After the menu is removed, the toplevel stays at y=menuHeight with the reduced height (e.g. 968 instead of 1003), leaving an empty strip.
.t, toggling -menu 6 times, fvwm/openbox/icewm): before, the toplevel height stays the same in every state, so adding the menu does not shrink it. With the original patch, the first removal and the first add are right, but the second removal leaves the toplevel at y=menuHeight with the reduced height. Cause: the requested height then equals configHeight (the size the WM refused earlier), so UpdateGeometryInfo takes the final else { return; } branch, where the patch had no layout. After my fix, all 6 toggles are correct on all 3 WMs.
unix withWindowManager, uses pause; fails before: yes (main, and also the original patch); passes after: yes (fvwm, openbox, icewm); skipped without a WM)
winPtr->changes.height != wrapper height - menuHeight → LayoutWrapper() check to the final else branch of UpdateGeometryInfo. Added test unixWm-64.1.
REPRODUCED (main, 9.0, 8.6, 8.5)
selection handle . h1; selection handle . h2 then selection get -type UTF8_STRING returns h1's value on all versions listed (STRING returns h2)
selection handle . h1; selection handle . h2; selection get -type UTF8_STRING. Before: h1's value ("Replaced Original"). After: h2's ("Replaced Replaced").
-type UTF8_STRING -format UTF8_STRING and the same Tcl handler proc would be treated as implicit. Tk_DeleteSelHandler uses the same heuristic.
form "UTF8_STRING" not defined). Windows has no implicit UTF8_STRING handler (utf8Atom is 0 under _WIN32), so the fix does not apply there. Added -constraints unix to select-14.2; select-14.3 passes on Windows. Backup: af31a84c91.patch.1024.
Status now: Closed (Fixed)
ttk-image-multiple-displays, in main, 9.0: Fix fde9dc2392: X error BadDrawable when using an image element created by "ttk::style element create" on another display. The images of an image specificatiotrunk, in main, 9.0: Fix for fde9dc2392: X error BadDrawable when using ttk::style element create with multiple displayscore-9-0-branch, in main, 9.0, 8.6: Fix for fde9dc2392: X error BadDrawable when using ttk::style element create with multiple displayscore-8-6-branch, in 8.6: Fix for fde9dc2392: X error BadDrawable when using ttk::style element create with multiple displaysREPRODUCED (main, 9.0, 8.6)
REPRODUCED (main, 8.6): partly by design, partly a real bug
<Control-h>. Before: "ab def ghi". After: " def ghi".
aaa bb ccc); now it deletes the selection (aaa ccc). entry already did.
REPRODUCED (main, 9.0, 8.6, 8.5, 8.4)
.f configure -background X on a gridded labelframe with -width/-height and a child produces 2 <Configure> per reconfigure (50x50 then back to the propagated 22x48); patched build: 0.
0 150 0 150, passes patched). frame, grid, pack, place tests: no new failures (pack-18.x, place-8.x and wm failures are pre-existing without a WM).
0 150 0 150); passes after: yes)
REPRODUCED (9.1 main, 8.6 tip), limitation / RFE (same as 11bd4a03a0)
-font {Helvetica 8} and at {Helvetica 40}. It is 51 px for both, on 9.1 and 8.6. Run 1 also showed that menubar.tcl draws Courier 24 bold in the system font.
Status now: Closed (Fixed)
static-tk-shared-tcl, in main, 9.0: Fix f458d44204: --disable-shared build failed against --enable-shared build of Tcl: the zip file of Tk was created from tclsh, which only contains the zip arctrunk, in main, 9.0: Fix f458d44204 to build --disable-shared Tk against --enable-shared Tclcore-9-0-branch, in main, 9.0: Fix f458d44204 to build --disable-shared Tk against --enable-shared TclREPRODUCED (main; same Makefile.in code in 9.0 and 8.7; 8.6 has no zipfs)
zip error: Zip file structure invalid (../libtk9.1b1.zip), make fails.
zip -A and then zip -rq fail.
Status now: Closed (Fixed)
x11-error-handler-sync, in main, 9.0: Fix 290ce5f460: Tk performance on X11 with forwarding decreased in 8.6.11.REPRODUCED (8.6 tip, 8.6.13, 8.6.15, 8.7, 9.0, main built with --disable-bidi). Regression came in 8.6.11 with check-in 7f20966df9 (2020-04-14, "Workaround for 3767882e06: BadLength..."). The installed main build does not show it.
lastRequest < firstRequest), which is the usual case for Xft text extents once glyphs are cached. Round trips drop from 2528 to 1735. font, unixFont and canvText tests pass. send-8.16, winfo-9.4 and winfo-9.7 fail with and without the patch (no WM). No automated test (round-trip count).
REPRODUCED (main, 8.6, 8.4). This is intentional old Motif-style behaviour.
event generate <<Paste>> with a selection on Xvfb. On main and 8.6, entry, spinbox and text insert after the selection ("aaa bbbXYZ ccc"), while ttk::entry replaces it ("aaa XYZ ccc"). 8.4 has the same behaviour for entry and spinbox.
<<Paste>>, library/spinbox.tcl <<Paste>> and library/text.tcl tk_textPaste delete the selection only when [tk windowingsystem] ne "x11". ttk::entry::Paste always calls PendingDelete.
<<Paste>> with "bbb" selected gives entry/spinbox/text "aaa bbb cccXYZ" (ttk::entry gives "aaa XYZ ccc") / after: the selection is deleted and the text is inserted at the insert cursor (entry-25.4 with icursor at the selection end gives "aaa XYZ ccc")
<<Paste>> bindings now read the CLIPBOARD first (if {![catch {::tk::GetSelection %W CLIPBOARD} tk::Priv(data)]}, the same pattern as <<Cut>>/<<Copy>>) and only then delete the selection. Without this, now that X11 also deletes, pasting from an empty clipboard deleted the selection and inserted nothing. Checked: an empty clipboard now leaves "aaa bbb ccc". tk_textPaste already reads the clipboard first. Remaining (unchanged) design point: like the existing Windows/macOS behaviour, the selection is deleted even when the insert cursor is elsewhere, and the text goes to the cursor (ttk::entry moves the cursor to sel.first first). Original kept as 3c4435c9ae.patch.1024.
aaa ccc); now they keep it (aaa bbb ccc). text kept it either way. entry 307/0, spinbox 324/0.
Status now: Closed (Fixed)
menu-post-under-pointer, in main, 9.0: Fix [470331], [680660], 1596662fff, f9d316a5e0: a menu posted over its menubutton or menubar entry invoked the entry under the pointer on the release of thetrunk, in main, 9.0: Fix for 470331ffff: Displaced menus do not stay open; 680660ffff: Menu items accidentally selected; 1596662fff: Menu behaviour at screen bottom; [f9d316a5core-9-0-branch, in main, 9.0, 8.6: Fix for 470331ffff: Displaced menus do not stay open; 680660ffff: Menu items accidentally selected; 1596662fff: Menu behaviour at screen bottom; [f9d316a5core-8-6-branch, in main, 9.0, 8.6: Fix for 470331ffff: Displaced menus do not stay open; 680660ffff: Menu items accidentally selected; 1596662fff: Menu behaviour at screen bottom; [f9d316a5menu-post-under-pointer, in main, 9.0: Add a widget demo for popup (context) menus posted with tk_popup, with menus of different sizes.REPRODUCED (main, 8.6, 8.4)
-direction below has the same problem: the menu is placed at 522..1024 on top of the button at 964.
vrooty + vrootheight + rooty - mh), which is then clamped back over the button.
rooty - mh (only when it fits). Tests menuDraw-17.3 and menubutton-10.1, which fail on unpatched main. The dropdown now opens above and stays posted after release. menu, menuDraw and menubut tests pass.
-direction below menubutton menus are shifted up over the button when they don't fit below, so the button release invokes an item. The fix is to post them above the button when they fit there.
REPRODUCED (9.1 main, 8.6 tip)
time = TkGetMS() (GetTickCount at *processing* time), not the time the click happened. When a <<ListboxSelect>> handler blocks 1.5 s, the queued second click gets a timestamp ~1.5 s later than the first, so it fails the double-click interval check in tkBind.c. X11 uses server timestamps, so the double click survives. macOS has the same pattern (TkGetMS in tkPointer), matching fvogel's observation.
9.1: ListboxSelect=2 Double-1=0, press times differ by 1516 ms. 8.6: same, 1547 ms.
With the prototype: ListboxSelect=1 Double-1=1. Control run: clicks 700 ms apart (Windows double-click time is 500) are correctly not a double click. bind, event, listbox, entry, text, button, scale, scrollbar and winfo tests: 2841 tests, 0 failed.
(Time)(DWORD)GetMessageTime() in InitializeEvent (under #ifdef _WIN32; tkPointer.c is only built on Windows and macOS) and in GenerateXEvent. There is no automated test, because it needs real queued input messages.
Caveat: for Tk_UpdatePointer calls that do not come from a message (the mouse timer, warp), GetMessageTime() returns the time of the last retrieved message. That time is slightly older, which is harmless for crossing events. macOS needs the equivalent ([NSEvent timestamp]); not done.
ListboxSelect=1 Double-1=1, OK
Status now: Open (Fixed)
aqua-photo-gamma-palette, in main, 9.0: Fix de6ef8276c: photo -gamma and -palette had no effect on macOS. Apply the fix for 32f2e19de8 to all platforms which render RGBA images, not only Windows: trunk, in main, 9.0: Fix de6ef8276c: photo -gamma and -palette had no effect on macOS.TkImgPhotoDisplay() currently being enabled by TK_CAN_RENDER_RGBA; probably the simplest way would be to disable the definition in tkMacOSXPort.h and leave TkpPutRGBAImage() unused. Is this acceptable? ``` --- macosx/tkMacOSXPort.h +++ macosx/tkMacOSXPort.h @@ -138,12 +138,14 @@ #define TK_HAS_DYNAMIC_CO…REPRODUCED on X11 (main, 9.0, 8.6) for images with partial transparency; on Aqua (and Windows on main since 3bbe54bc74, 2026-06-15, which defined TK_CAN_RENDER_RGBA in tkWinPort.h) for all images
REPRODUCED (main, 8.6 on X11)
itemconfigure -fill red 561 black pixels remain at x=240..270.
bbox, which many tests depend on; not small)
TkCanvTextRedrawMargin() in tkCanvText.c returns (ascent+descent)/4 for a visible text item. New static GetItemRedrawArea() in tkCanvas.c returns the item bbox grown by that margin on all four sides (this also covers -angle). It is used in EventuallyRedrawItem, in the 4 old-area sites and in the DisplayCanvas item-selection loop. bbox, find and the item header are unchanged. Measured overhang at -100px is at most 17px (DejaVu/Noto/Liberation/Free italic); the margin there is 25-34px. Not changed: the image subcommand (DrawCanvas) still selects items by bbox. 9fd94c63b0.patch (162 changed lines: about 60 are function header comments, 20 are the test, and the EventuallyRedrawItem change is mostly renaming itemPtr->x1 to local x1. That is over the 60-line guideline. It could be made smaller, e.g. by inlining the margin in EventuallyRedrawItem only, but then the display loop and the old-area sites stay wrong.)
update so the overhang is drawn, deletes the item, and counts non-white pixels in bbox±30 with testpixel (constraint testpixel). Fails before: yes (main: non-zero). Passes after: yes. With fontconfig all of Times/Helvetica/DejaVu/Liberation italic "f" overhang. If a platform's Times italic f has no overhang, the test passes trivially.
bbox unchanged but enlarges the redraw area of text items by a quarter of the line height (test canvText-23.1).
REPRODUCED (main): verified from the main source, no live test this round
REPRODUCED (main, 8.6)
.t on main and 19/20 on 8.6. With openbox, 12-15/20 on main (0/20 on 8.6 in one run, so the race is timing dependent). fvwm and no WM: 0. twm: no Leave events generated.
child == wmPtr->reparent), it returns the toplevel without checking that it is still mapped. After wm withdraw the WM destroys/unmaps the frame asynchronously, so for a short time the frame still covers the point.
!Tk_IsMapped(wmPtr->winPtr)). After the patch: icewm 0/20 and openbox 0/20 (2 runs each). winfo/unixWm/wm tests show the same results as unpatched (no WM), and unixWm.test passes fully under icewm. No new test (needs a reparenting WM).
<Leave> reported .t / after 0/20 and 0/20 (20 Leave events still delivered)
winfo containing right after after 200); 3 reruns passed and unpatched passed 2/2, so I count it as a WM timing flake, but it could be re-checked.
continue the search descends into the stale frame, where the unmapped wrapper is not found, so it returns NULL. That is correct. Pre-existing, unrelated: the return NULL in the title-bar branch leaks the error handler.
REPRODUCED (main, 9.0, 8.6), as designed. This is a behaviour change or enhancement rather than a bug. The documentation does not specify the order.
-zoom 2 -subsample 3 on 9.1b1, 9.0.5 and 8.6.18 gives 000 000 333 333 666 666 in 6x2 (subsample first). With the patch it gives 000 111 333 444 666 777 in 6x1.
copy -zoom -subsample, so it should go only to 9.1 and be documented as an incompatibility (or via a TIP).
-zoom 2 -subsample 3 of 8 pixels gives 000 000 333 333 666 666 / after 000 111 333 444 666 777
int yProgress = 0; and int xProgress = 0; are now declared at the top of the function. The pixel loop body is re-indented one level, because the removed xRepeat loop left it over-indented. The long srcPtr =/srcLinePtr = lines are wrapped. I checked the logic, including the negative subsample mirror (C truncation gives the correct mirrored index) and tiling. No functional bugs found. The per-pixel division replaces the old repeat loop, which may be slower for large zooms.
REPRODUCED (main, 9.0, 8.6), but NOT-A-BUG in Tk (the Thread package's event proc ignores the event mask). The reporter withdrew the ticket in their last comment.
after 300 after thread::send -async. With that change: when wm geometry runs before update idletasks, the result is {B A} every time; without it, {A B} (as expected).
update idletasks runs the idle UpdateGeometryInfo. That calls unix/tkUnixWm.c:WaitForEvent → tkUnixEvent.c:TkUnixDoOneXEvent, which calls Tcl_ServiceEvent(TCL_WINDOW_EVENTS) to wait for the ConfigureNotify. Thread's ThreadEventProc ignores its mask argument and so runs even for a TCL_WINDOW_EVENTS-only service. Event procs are supposed to return 0 for flags they don't handle.
mask & TCL_FILE_EVENTS; changing Tk's nested wait would be risky)
REPRODUCED (main, 8.6). This is intentional behaviour since 8.6.11 (3ccd19e0a7 for d91e05bf20), so it is a design dispute.
focus $w unconditionally, whatever the state.
-takefocus 0. This matches the recent ttk::notebook fix 3de1b72157. Normal-state behaviour is unchanged. text.test passes (689/0 failed).
-takefocus 0: a disabled text widget with -takefocus 0 no longer grabs the focus on click, as with ttk::notebook 3de1b72157. Patch and test text-39.1 on a branch.
Status now: Open
unix-zipfs-mkzip, not merged: Fix 130949dafe: build fails without zip: no rule to make minizip. The autoconf builds (unix and MinGW) used an external zip program to create the Tk library aREPRODUCED (main, 9.0); 8.6 not affected (no zipfs)
ac_cv_path_zip=no configure --with-tcl=... and then make tkzipfile. Trunk: No rule to make target "minizip", needed by "libtk9.1.1.zip"; 9.0.5: same, for libtk9.0.5.zip. User's branch unix-zipfs-mkzip (d399f15e5f), same setup: full make succeeds. wish with TK_LIBRARY unset gets tk_library = //zipfs:/lib/tk/tk_library; msgs/ttk/images are directories with 18/26/13 entries. The archive differs from the zip-made one only in missing explicit directory entries (harmless).
Status now: Closed (Fixed)
dialogs-after-auto-reset, in main: Fix 3da0592db4: after [auto_reset], the Tk file dialogs failed with "invalid command name .__tk_filedialog.contents.icons" (X11), or with "Duplicate element Ctrunk, in main, 9.0: Fix for 3da0592db4: Filesystem dialogs conflict with auto_reset (under Linux)core-9-0-branch, in 9.0, 8.6: Fix for 3da0592db4: Filesystem dialogs conflict with auto_reset (under Linux)core-8-6-branch, in 8.6: Fix for 3da0592db4: Filesystem dialogs conflict with auto_reset (under Linux)REPRODUCED (main, 9.0, 8.6); 8.5 OK (no TclOO iconlist)
REPRODUCED (9.1 main, 8.6 tip)
wm attributes -topmost 1, added for bug 1991930. The combobox does get <Visibility> VisibilityFullyObscured events on X11.
-topmost from the posted popdown gives the same picture, but this is inconclusive: in the scheduled-task session the other process cannot take the foreground (Program Manager stays the foreground window), so it is not a real activation.
-topmost 1 on Windows); nothing unposts it when another application appears
pause 200 instead of after 200 {set done 1}; vwait done
REPRODUCED (main, 8.6, 8.4). Arguably NOT-A-BUG (cannot work).
place .marker -in .#m -relx .5 -rely .5 puts the marker a menubar height too low (y 153 instead of 117 on main); x is correct.
REPRODUCED (main, 8.6)
XSetClipRectangles(gc, 0,0,30x40) and calls Tk_DrawChars. Text is drawn out to x=252, so the 30px clip is ignored on both versions.
XftDrawSetClip() from the thread-global tsdPtr->clipRegion, which is set by the private TkUnixSetXftClipRegion() (used only by ttkLabel/ttkEntry). The GC clip mask is never used, and Xlib gives no way to read it back from a GC. Also, Tk_ClipDrawableToRect (stub 284) is NULL/no-op on X11 and Windows.
Tk_ClipDrawableToRect on X11 so it sets/clears the Xft clip region (this fills the NULL stub slot and removes the #undef/#define ... 0 in tkDecls.h/tkStubInit.c for non-Mac), or export TkUnixSetXftClipRegion through the platform stubs.
Tk_ClipDrawableToRect(), which is a no-op on X11 today and could set the Xft clip region.
#define Tk_ClipDrawableToRect 0 for every non-Mac build, and tkDecls.h has #undef for non-Mac. A stubs extension that calls it on main segfaults (verified).
HAVE_XFT || HAVE_BIDI, and clears and frees it when width or height is negative. Without Xft it is a no-op, because core X fonts already honour the GC clip. The drawable argument is ignored: the clip applies to all Xft text drawing in the thread until reset. Only Xft text is clipped, not other Xlib drawing; the docs should say so (doc/3DBorder.3 is not updated yet). Stub table: no regeneration. tk.decls and the generated part of tkDecls.h are unchanged. In tkStubInit.c #else #define ... 0 became #elif defined(_WIN32). In the hand-written tail of tkDecls.h (below !END!) #ifndef MAC_OSX_TK became #ifdef _WIN32. So the slot is filled on X11, and Windows keeps the NULL slot. 4476fd6144.patch (63 changed lines, about 25 of them comments).
testfont drawclipped font window text x y w h, ~30 lines) plus a testpixel check. Left out to keep the change under ~80 lines.
REPRODUCED (main, 8.6)
icursor end the cursor is drawn at the right edge of the word (screenshot work-a2/1e9d743997-main.png). .e bbox 0 is at x=3, i.e. index-to-x mapping stays logical LTR. 8.6 does not shape or reorder at all.
Status now: Closed (Fixed)
cursor-file-tests, in main, 9.0: Fix e1d86b048b: -cursor options: documentation. Fix the corrupted reference to the X cursor font (cursorfont.h), document that the cursor colors are only supptrunk, in main, 9.0: Fix e1d86b048b: -cursor options: documentation improvementscore-9-0-branch, in main, 9.0: Fix e1d86b048b: -cursor options: documentation improvementscursor-file-tests, in main, 9.0: Rebase to trunkREPRODUCED (main, 8.6), but it is not what the ticket assumes. The forms are documented in GetCursor.3 (and options.n refers to it). On X11 {name fg bg} colors are ignored because libXcursor replaces a glyph cursor from the cursor font with the themed ARGB cursor whenever source font == mask font and mask = source+1, and it ignores the colors (with XCURSOR_CORE=1 the colors work). {name fg} and @src fg / @src mask fg bg do work. @src alone is documented as Windows-only (the ticket's failing .xbm test). There is also a doc typo in GetCursor.3: "standard X cursor cursor", "cursorcursor.h" (should be cursor font / cursorfont.h).
{watch red blue} now shows red/blue, while watch and {watch black white} keep the themed cursor. cursor.test passes. No automated test (it would need XFixes).
{name fg bg}. The branch uses a separate mask font ID when colors are given, so they are honoured again. The @file forms work as documented (@file alone is Windows-only).
Status now: Closed (Fixed)
REPRODUCED (main, 8.6 source: generic/tkEvent.c still creates an XIC for every window on its first event (TK_CHECKED_IC)). A fix already exists on branch x11-lazy-xic 894c1665c5 (2026-09-23, fixes the duplicate 5d52ad92fa); not merged yet.
::tk::dialog::error::bgerror, falls back to ::tkerror and is im…REPRODUCED (main): still an open design item. library/bgerror.tcl still defines ::tk::dialog::error::bgerror, falls back to ::tkerror and is imported as global bgerror. library/console.tcl:55 and library/fontchooser.tcl:347 still call bgerror directly.
interp bgerror); Tk never switched to installing a handler with interp bgerror.
bgerror/tkerror). A small first step: make console.tcl and fontchooser.tcl call {*}[interp bgerror {}] $msg $opts (or after 0 [list error ...]) instead of bgerror.
bgerror directly. Moving to interp bgerror (TIP 221) is an RFE, so maybe retype it.
bgerror directly, which bypasses a handler installed with interp bgerror (TIP 221). A grep of library/ (outside bgerror.tcl and msgs) finds no other direct calls to bgerror/tkerror, and generic/ and unix/ have none either.
catch {...} err opts followed by {*}[interp bgerror {}] $err $opts. This is synchronous, like before. With the default handler (::tcl::Bgerror) it still ends up in Tk's bgerror dialog, so nothing changes for users who did not install a handler. 162257a827.patch (33 changed lines, 4 library + 29 test)
-command error goes to ::bgerror even with an interp bgerror handler installed / after: the installed handler gets it (msg and options dict)
interp bgerror and a recording proc bgerror, then clicks Apply with -command {error oops}) (fails before: yes, result {bgerror oops}; passes after: yes, {handler oops}). The console.tcl change has no test: the error path needs menu .menubar to fail inside the console interp at init.
{*}[interp bgerror {}] instead of calling bgerror directly, so TIP 221 handlers are honoured. Moving bgerror.tcl itself to an interp bgerror handler (and dropping the tkerror fallback) is a compatibility decision, closer to an RFE.
Status now: Open
header-dependencies, not merged: Fix a0109510a8: make did not rebuild object files after a header file was changed. If the compiler supports -MMD -MP (gcc, clang) and make supports -include (header-dependencies, not merged: Header dependencies on Windows: the same for win/Makefile.in (MinGW, MSYS2, Cygwin), and pass the compiler options to mkdepend.tcl in the depend target of win/mREPRODUCED (main). In unix/Makefile.in, object rules list only their .c file (plus a few tkUuid.h/tkImgPhoto.h cases). Touching generic/tkButton.h or unix/tkUnixDefault.h rebuilds nothing. win/Makefile.in has the same problem.
touch a header, then make -n, gives 0 compiles before the patch and 137 after.
$(OBJS) $(WISH_OBJS) $(TKTEST_OBJS) $(STUB_LIB_OBJS): $(DEP_HDRS), where DEP_HDRS is generic/*.h, ttk/*.h and unix/*.h (X11) or macosx/*.h + xlib (Aqua). Any header change rebuilds all objects. The rule sits after all:, so the default goal is unchanged. A finer alternative is -MMD -MP with -include *.d (gcc/clang only). win/Makefile.in would need the same rule.
f436621c1a REPRODUCED (9.1 main, 8.6 tip), prototype verified. 2045553fff REPRODUCED ("" and absent differ); doc prototype verified and extended.
-defaultextension "" does NOT disable the guess, which is the opposite of what the 2026 anonymous comment asks for.
*.ext pattern of the initially selected filter and calls SetDefaultExtension. The Common Item Dialog is expected to update it when the user changes the type; this needs checking on Windows. An explicit -defaultextension "" still disables it. Repro: win/f436621c1a.tcl (interactive; type "foo" in 4 cases; prints OK/DIFFERS per case).
foo (case 1), and also foo after switching to Text (case 2). -defaultextension "" gives the type's extension (foo.tcl, or foo.txt with Text selected). 2045 script: "" gives myfile.xyz, absent gives myfile.
-defaultextension .dat with first type {"All files" *} gives foo.dat; with first type {Text .txt} gives foo.txt; with {"Tcl or Text" {.tcl .txt}} gives foo.tcl. On Windows the extension of the selected type wins over -defaultextension (on Unix an explicit -defaultextension wins, see tkfbox.tcl SetFilter).
foo.tcl, case 2 foo.txt (follows the type selector). 2045 script: both give myfile.xyz. The dx.tcl results do not change.
SetDefaultExtension(L"") (7 code lines), replacing the earlier filter-parsing version. It includes getOpenFile.n text for the patched behaviour and the two tests. 2045553fff.patch (doc only, for unpatched behaviour) is updated with the rule that the selected type's extension wins on Windows. Use one of the two doc texts, depending on whether f436 goes in.
bar / after: bar.txt and bar.tcl
Status now: Open
win-canvas-arc-stipple, in main, 9.0: Update changes.mdREPRODUCED (9.1 main); FIXED on branch win-canvas-arc-stipple
REPRODUCED (main, 8.6)
.b ends up at x=6 (main) / x=11 (8.6), while the inner area starts at x=45 (bd 20 + highlight 25). The ghosts/vapor trails only seen in revised_text were fixed in 94547cbef7 (closed).
REPRODUCED (main, 8.6). It is closer to an RFE: the current behaviour is deliberate fallback code.
-initialdir /nonexistent/sub -mustexist 0 the dialog opens in [pwd] and the entry shows [pwd].
-initialdir <fake>/sub -mustexist 0, the dialog starts in [pwd] and the entry shows [pwd]. After, it browses the nearest existing ancestor and the entry shows <fake>/sub; OK twice returns that path.
set afterId [after 50 ...] and cancels it in a new -cleanup. On unpatched main the dialog closes after the first OK, and the pending press then hit 4.5's dialog, which cascaded into failures of 4.5 and 5.1. Now only 4.4 fails without the fix. Backup: 964af13db0.patch.1024.
REPRODUCED (revised_text 8b6e012e5d, 2026-09-15). Not applicable to main/8.6 (no -spacemode option there).
REPRODUCED (main, 8.6) for part (b), the "arrows" drawn with tags that combine -tabs and -justify right. Fixed on revised_text. Parts (a) and (c) were script errors or are fixed on revised_text. On revised_text, textDisp-2.26 and textDisp-24.24 are still marked knownBug and still fail if forced (2.26: 48 78 108 138; 24.24: {14 7 7 13} {28 20 7 13}), because the branch intentionally applies tabs under right/center justify.
TK_DRAW_IN_CONTEXT branch of CharDisplayProc. On main, unix/tkUnixInt.h defines TK_DRAW_IN_CONTEXT only #ifdef HAVE_BIDI, so a --disable-bidi build (and every non-bidi build) still drew the HT glyphs. I added the same run-between-tabs drawing to the #else (Tk_DrawChars) branch. VERIFIED in both builds.
-tabs {2c 4c}, text "a\tb\tc\td e", compared pixel by pixel with "abcd e".
#else /* !TK_DRAW_IN_CONTEXT */ hunk, which loops over runs separated by tabs and advances x with MeasureChars, treating tabs as 0 width. Underline and overstrike are drawn per run. Backup: a34b49f8c6.patch.1024.
Status now: Open
x11-embed-focus-return, in main, 9.0: Fix a4fa3ad2d6: event misbehavior with certain widgets when embeddingmistake, not merged: Fix a4fa3ad2d6: event misbehavior with certain widgets when embeddingmistake, not merged: Fix a4fa3ad2d6: event misbehavior with certain widgets when embeddingx11-embed-focus-return, not merged: unixEmbed tests a4fa3ad2d6: make the focus tests independent of the previous tests. Restart the child process in the cleanup of unixEmbed-5.4 before destroyinx11-embed-focus-return, not merged: Merge main. Main contains the earlier check-ins of this branch in its history, but not the fix for a4fa3ad2d6 and test unixEmbed-5.4, which the merge removed;embed-container-destroyed-pixmap, not merged: Merge main.x11-implicit-focus-release, in main, 9.0: Adapt regression test to use new utility proc "movePointerAwayFromTestArea" and move test constraint noWindowManager to a dedicated LOCAL TEST CONSTRAINTS sectix11-embed-focus-return, not merged: Merge main.REPRODUCED (main). The fix exists on branch x11-embed-focus-return (eb2b41d5b3, test 63c88e8a6d, f98ef68b49, 11bfb3794d) and is not merged into main yet. Main's generic/tkFocus.c still ignores FocusIn/NotifyInferior, and so do 9.0 and 8.6.
REPRODUCED (main, 9.0, 8.6)
ttk::frame -relief groove holding a label, after update idletasks. Before, the frame's reqsize equals the label's in every theme (default 36x22, clam/alt 38x24). After: default/classic 38x24 vs label 36x22, clam/alt 42x28 vs 38x24.
Status now: Closed (Fixed)
win-zoomed-geometry, in main, 9.0: Fix 557441302b: wm geometry returns wrong position for zoomed toplevels. On Windows the position of the restored window was reported with the size of the zoomwin-zoomed-geometry, in main, 9.0: Fix 557441302b also for a toplevel iconified from zoomed: on Windows wm geometry reported the position of the restored window while it was iconified. Tests wmtrunk, in main, 9.0: Fix for 557441302b: wm geometry returns wrong position for zoomed toplevelscore-9-0-branch, in main, 9.0, 8.6: Fix for 557441302b: wm geometry returns wrong position for zoomed toplevelscore-8-6-branch, in 8.6: Fix for 557441302b: wm geometry returns wrong position for zoomed toplevelsREPRODUCED (9.1 main, 8.6 tip); prototype verified
-zoomed 1, wm geometry reports the zoomed position (+0+0 / -4-4).
+-8, work-win/557441302b.tcl): ref91 and 8.6 report zoomed 1023x697+303+175 (the restored position). The prototype reports 1023x697+-8+-8 (the real frame position; rootx=0, rooty=23), and restore gives back 200x200+303+175. The new test winWm-11.1 fails on ref91 and passes with the prototype. wm, winWm, winDialog, menu and winMenu tests: 1096 tests, 0 failed.
+-8+-8 for the off-screen frame border. Tk parses this back as an absolute position.
wm geometry report the position of the maximized window (e.g. +-8+-8) while the restored geometry is kept. Test winWm-11.1 is included.
+-8+-8, and restore gives 200x200+303+175)
unset res x y was added to its cleanup. 557441302b.patch is the current file. 557441302b.patch.new is the older code-only version (the same code, without the test) and can be deleted.
REPRODUCED (main, 8.6)
. configure -menu .n in a maximized window, the new menubar is 1 px high and the toplevel is placed at y=1 in the wrapper.
. configure -menu .n): before no mapped menubar and toplevel rooty=22 / after menubar .#n mapped with h=35 and toplevel rooty=56 (same after switching back to .m)
Status now: Closed (Fixed)
x11-keep-wm-state, in main, 9.0: Fix fecd6bd2fa: linux only: window -zoomed attribute is restored when it should not be. CheckNetWmState only updated the current attributes, so mapping the witrunk, in main, 9.0: Fix for fecd6bd2fa: linux only: window -zoomed attribute is restored when it should not be.core-9-0-branch, in main, 9.0, 8.6: Fix for fecd6bd2fa: linux only: window -zoomed attribute is restored when it should not be.core-8-6-branch, in main, 9.0, 8.6: Fix for fecd6bd2fa: linux only: window -zoomed attribute is restored when it should not be.REPRODUCED (main, 8.6)
wm attributes -zoomed 1. Same for -topmost and -fullscreen.
Status now: Closed (Fixed)
x11-pixmap-size-limit, in main, 9.0: Fix bffa794b1b: BadAlloc (insufficient resources for operation) in the grid command.trunk, in main, 9.0, 8.6: Fix for bffa794b1b: "BadAlloc (insufficient resources for operation)" in the grid command.core-9-0-branch, in main, 9.0: Fix for bffa794b1b: "BadAlloc (insufficient resources for operation)" in the grid command.core-8-6-branch, in main, 9.0, 8.6: Fix for bffa794b1b: "BadAlloc (insufficient resources for operation)" in the grid command.trunk, in main, 9.0, 8.6: Test unixbutton-3.1: place the huge widgets instead of gridding them. The gridded toplevel exceeded the 16-bit limit of X window sizes, and if it was already maREPRODUCED (main, 8.6)
Status now: Closed (Fixed)
pointer-dead-restrict-window, in main: Fix 131adc6b77: on Windows and macOS, when the window that got a ButtonPress was destroyed while the button was down, the following ButtonRelease and Motion etrunk, in main, 9.0: Fix for 131adc6b77: bound buttonpress is passed on to other programcore-9-0-branch, in 9.0, 8.6: Fix for 131adc6b77: bound buttonpress is passed on to other programcore-8-6-branch, in 8.6: Fix for 131adc6b77: bound buttonpress is passed on to other programREPRODUCED (9.1 main, 8.6 tip)
. ButtonRelease-1 reaches the window below, in both cases (the press does not leak, and there is no Double-1). With the prototype: no events below in either case. bind, event, grab, winfo, frame, button, listbox, entry, text, scale, scrollbar and menu tests: 3630 tests, 0 failed.
restrictWinDead flag, set in TkPointerDeadWindow when buttons are down, makes Tk_UpdatePointer discard button and motion events until all buttons are released, then restores the grab capture. No automated test: event generate does not go through Tk_UpdatePointer. macOS gets the same change (untested).
REPRODUCED (main, 8.6)
tk_atk_accessible_finalize.
1. The per-display cache in libXrender/libXft goes stale once one thread's display has been closed with XCloseDisplay (TkpCloseDisplay at thread exit) and another thread opens a new one. Tk's own font code has only thread-specific data.
2. main only (a new regression): unix/tkUnixAccessibility.c keeps process-global unlocked state (tk_to_atk_map, toplevel_accessible_objects, tk_root_accessible, acc_context), so ATK is not thread-safe.
REPRODUCED (main, 8.6); this is a design question more than a bug
font delete on a named font that is still in use only marks it deletePending. Widgets that hold it (and new widgets that ask for the same name while it is held) keep the old attributes. After the last reference goes away, "TkFixedFont" etc. are parsed as a font description with an unknown family. They then fall back to the system default (here Noto Sans 12, proportional), so the text widget metrics change. Recreating the named font updates all users. font configure TkFixedFont errors even while the font is still effectively in use.
font delete refuse, or reset instead, for the Tk* standard fonts?
REPRODUCED (main, 9.0, 8.6, 8.5); duplicate of af31a84c91 / [2443069]
selection get -type UTF8_STRING still returns h1
REPRODUCED (main, 8.6). Holding Button-1 in the ttk trough pages all the way to the end instead of stopping at the pointer. On X11 the classic tk::scrollbar does the same (it is not native there); the native win32 scrollbar stops at the pointer. The "trough turns dark while pressed" part is a theme/visual issue and not addressed.
ttk::Repeatedly Scroll $w ±1 pages repeats unconditionally until release.
1 0. After, it stops at the pointer and the result is 1 1.
after 3000 {set done 1} ; vwait done is replaced with pause 3000. Backup: d1d4286dda.patch.1024.
REPRODUCED (main, 9.0, 8.6); not in 8.5, 8.4
find enclosed = "" after -text "". 8.5.19 and 8.4.20 give 1. find overlapping works on every version, and angled empty text is found.
find enclosed on "" and "\n" items gives {} {} / after {1 2} {}
_. ttk::treeview is installed as ttk_treeview.n alt…Status now: Closed (Fixed)
man-colon-names, in main, 9.0: Fix 3604346fff: "::" in manual page names was replaced with "_" on installation, so "man ttk::treeview" did not find the page. Keep ":" in the names, and instman-colon-names, in main, 9.0: Merge-markREPRODUCED (main, 8.6). unix/installManPage still maps every non-alphanumeric sequence to _. ttk::treeview is installed as ttk_treeview.n although its .TH/NAME says ttk::treeview. Tcl's installManPage (tclmain) does the same.
s/[^ A-Za-z0-9][^ A-Za-z0-9]*/_/g from dkf's a7eee0499a (2012)
: is kept, so pages install as ttk::treeview.n, tk::mac.n, safe::loadTk.n, etc. I checked all of doc/*: only :: names change. It is a policy decision, and Tcl's installManPage would need the same change.
:: to _, so man ttk::treeview fails. Branch bug-3604346 (7de29bd83e) keeps : in page file names; this needs a decision (together with Tcl) whether to merge it or close as won't-fix.
REPRODUCED (9.1 main, 8.6 tip); prototype verified
[wm state $top] eq "zoomed" (Windows/macOS) or [wm attributes $top -zoomed] (X11). Verified on X11/openbox that a press no longer starts a drag on a zoomed window; ttk.test passes. The patch does not hide the grip or change the cursor; hiding is an RFE.
wm attributes -zoomed 1, then press and drag the sizegrip by -100,-100, then unzoom). Unlike the triage note, this does reproduce on X11. openbox before: restored size 1180x903 (wrong), after: 200x150. icewm before: 1180x878, after: 200x150. Without a WM, -zoomed is never set, so the result is the same before and after.
Status now: Open
default-maxsize-workarea, not merged: Fix 3598564fff: the default maximum size of a toplevel did not take into account the taskbar or panels, so a window whose natural size was larger than the scrdefault-maxsize-workarea, not merged: Fix 3598564fff: the default maximum size of a toplevel did not take into account the taskbar or panels, so a window whose natural size was larger than the scrdefault-maxsize-workarea, not merged: Rebase to mainREPRODUCED (9.1 main, 8.6 tip)
defMaxWidth/Height come from WM_GETMINMAXINFO ptMaxTrackSize, which is the whole screen and not the work area, so the natural size is clamped only to the screen height. A fix would clamp the default (not the user-set) maxsize to the monitor's rcWork (GetMonitorInfo). That changes behaviour and could also restrict manual resizing, so it needs discussion.
wm maxsize=1027x749, and the window bottom is at 780: below the task bar and even below the screen.
Status now: Closed (Fixed)
wm-forget-release-menubar, in main, 9.0: Fix 3515522fff: [wm forget] did not release the menubar of the toplevel, so destroying it or the menu later crashed on Windows (TkWinGetWrapperWindow() derefeREPRODUCED (9.1 main, 8.6 tip, 8.5.19): win/3515522fff.tcl crashes with an access violation (exit code -1073741819)
wm forget the toplevel becomes a frame but keeps its menubar registration: the menu's topLevelList entry and the MENUBAR clone with parentTopLevelPtr set. On Windows, later destroying the clone's .system cascade calls TkWinGetWrapperWindow (win/tkWinMenu.c TkpDestroyMenu), which dereferences the now-NULL wmInfoPtr. On 8.6 X11, forget+manage leaves a stale duplicate entry that is used after the window is freed.
wm forget leaves the menubar registered to the former toplevel, so the Windows system-menu code later dereferences a NULL wmInfoPtr. 8.6 on X11 also crashes after forget/manage/destroy. Fix prototype: release the menubar in TkMapTopFrame when a toplevel becomes a frame, and guard TkWinGetWrapperWindow. Needs testing on Windows.
wm forget the menubar stays registered, and TkpDestroyMenu → TkWinGetWrapperWindow dereferences a NULL wmInfoPtr.
wm forget. Fix: release the menubar when a toplevel becomes a frame, and guard TkWinGetWrapperWindow; test wm-forget-2.2.
toplevel .t -menu .m; wm forget .t; destroy .m; menu .m creates a menubar clone .t.#m inside the frame .t. After wm manage .t there are two clones (.t.#m, .t.#m1). With the patch: no clone while forgotten, and exactly one after manage.
REPRODUCED (9.1 main, 8.6 tip)
wm geometry does change (64x30 -> 64x24).
wm geometry change. Probably a tkWinWm.c issue.
wm geometry stays 64x30 and then becomes 64x28.
wm geometry reports 64x24. The triage guess about ConfigureTopLevel was wrong: both platforms convert the size back in the same way.
wm geometry stays 64x30. After: 518x490 throughout, wm geometry 64x24, identical to X11 (Xvfb, no WM: 520x522, 64x24).
Status now: Closed (Fixed)
menu-new-entry-error, in main, 9.0: Fix 3464070fff: when a menu entry could not be created, MenuNewEntry() freed it but left it in the entries array, and on Windows no error message was set. TheREPRODUCED (9.1 main, 8.6 tip); prototype verified and extended
$m add on 9.1 as an error). ref91: after 61405 entries the error message is empty, errorcode NONE, and the menu is broken afterwards (entrycget end -label gives "unknown option -label", from the dangling freed entry). 8.6: the same after 61403 entries. Prototype: "No more menu entries can be allocated." / TK MENU SYSTEM_RESOURCES, and the menu stays consistent. Also found: after deleting the last entry, adding one still failed, because GetNewID stopped the search before trying the last allocated ID. Fixed as well, and adding after a delete now works. menu.test and winMenu.test pass (part of the 1096).
$m add fails with an empty message and leaves a dangling entry. The patch sets an error message, removes the slot, and also fixes GetNewID never reusing the most recently freed ID.
TK MENU SYSTEM_RESOURCES, a consistent menu, and add-after-delete works
Status now: Closed (Fixed)
tk-dialog-over-parent, in main, 9.0: Fix 3414693fff: tk_dialog is centered over its parent window, like tk_messageBox and other Tk dialogs, not on the screen.REPRODUCED (main, 8.6)
::tk::PlaceWindow $w with no anchor, i.e. screen center ("Motif style"). tk_messageBox, tk_chooseColor, tk_chooseDirectory, tkfbox and fontchooser all use PlaceWindow $w widget $parent.
Status now: Closed (Fixed)
spinbox-fill-height, in main, 9.0: Fix [3313032]: ttk::spinbox does not expand its height. The field of the default TSpinbox layout fills the whole height of the spinbox, as in the classic and vitrunk, in main, 9.0, 8.6: Fix for 3313032fff: ttk::spinbox doesn't expand its height on Linux.core-9-0-branch, in main, 9.0: Fix for 3313032fff: ttk::spinbox doesn't expand its height on Linux.core-8-6-branch, in main, 9.0, 8.6: Fix for 3313032fff: ttk::spinbox doesn't expand its height on Linux.REPRODUCED (main, 9.0, 8.6)
-fill both -expand 1 at 100 px height, identify element in the middle of the spinbox gives the background, not textarea, in default/clam/alt. The classic theme is fine because its layout uses FILL_BOTH. ttk::entry and ttk::combobox are fine.
Spinbox.field is TTK_PACK_TOP|TTK_FILL_X, so the field keeps its requested height. The classic, vista and Wide.TSpinbox layouts use -sticky nswe.
REPRODUCED (main, 8.6) for embedded windows only. NOT-A-BUG for canvas items.
winfo viewable is 0.
Status now: Closed (Fixed)
vista-spinbox-arrows, in main, 9.0: Fix [3301552]: ttk::spinbox -font does not resize buttonstrunk, in main, 9.0, 8.6: Fix for 3301552fff: ttk::spinbox -font does not resize buttons.core-9-0-branch, in main, 9.0: Fix for 3301552fff: ttk::spinbox -font does not resize buttons.core-8-6-branch, in main, 9.0, 8.6: Fix for 3301552fff: ttk::spinbox -font does not resize buttons.REPRODUCED (main, 8.6), cosmetic
REPRODUCED (main 9.1b1, 9.0.5, 8.6.18, 8.5.19, 8.4.20)
[.#menu entrycget end -menu] before and after) on all listed versions, no WM needed
cascadeEntryChanged == false), the same objv is still passed to ConfigureMenuEntry for every clone. So -menu .menu.sub overwrites the clone's -menu .#menu.#menu#sub with the original, non-clone menu.
Screen struct (no RandR code in tkmain/unix). The fix is on branch …REPRODUCED on main and 8.6 by code inspection: main still only reads the Xlib Screen struct (no RandR code in tkmain/unix). The fix is on branch x11-randr-screen-size (ae3b099be2, 2026-09-18), not merged.
xrandr --fb/--newmode, and Xephyr/Xorg-dummy would need another display. I merged ae3b099be2 into a main checkout:
WidthOfScreen()/HeightOfScreen(), which Xlib only updates after XRRUpdateConfiguration().
bind Text <KP_Enter> is still # nothingREPRODUCED (main, 9.0, 8.6, 8.5, 8.4). bind Text <KP_Enter> is still # nothing
bind Text <KP_Enter> on main/9.0/8.6/8.5/8.4.20. With the patch, event generate .t <KeyPress> -keysym KP_Enter inserts a newline on the wt build. Without it the # nothing binding fires instead
<KP_Enter> to # nothing (so that the \r character is not inserted), and no binding makes it act like Return. Jan marked this as a dup of b3a1b9852d (the same problem for all widgets) and proposes a TIP to map KP_Enter to Extended-Return on X11.
bind Text <KP_Enter> [bind Text <Return>] replaces the # nothing binding). New test text-40.1. text.test passes. This fixes only Text; the generic fix proposed in b3a1b9852d would make it unnecessary.
no keycode for keysym "KP_Enter" (event generate -keysym KP_Enter); the repro also gives no newline. Windows has no KP_Enter keysym until 787402ffff (phase 1, bind-38.1) is applied. The patch is unchanged; commit it after 787402ffff, or give text-40.1 a constraint.
Status now: Closed (Fixed)
win-transient-keep-wrapper, in main, 9.0: Fix 3009885fff: tk_messageBox can return empty string on Windows.trunk, in main, 9.0: Fix 3009885fff: tk_messageBox can return empty string on Windowscore-9-0-branch, in main, 9.0, 8.6: Fix 3009885fff: tk_messageBox can return empty string on Windowscore-8-6-branch, in main, 9.0, 8.6: Fix 3009885fff: tk_messageBox can return empty string on WindowsREPRODUCED (9.1 main, 8.6 tip)
., returns {} right after wm deiconify . (3528 ms), with no click. wm frame .t changes (0xd50102 → 0xaf1b32), so the transient's wrapper was recreated.
Status now: Closed (Fixed)
wm-geometry-size-only, in main, 9.0: Fix [2995339]: setting only the size with wm geometry moves the window under some window managers. ParseGeometry no longer re-sends the position recorded from ttrunk, in main, 9.0: Fix for 2995339fff: ttk::sizegrip strange behaviour.core-9-0-branch, in main, 9.0, 8.6: Fix for 2995339fff: ttk::sizegrip strange behaviour.core-8-6-branch, in main, 9.0, 8.6: Fix for 2995339fff: ttk::sizegrip strange behaviour.REPRODUCED (main, 8.6, 8.4 core cause) with metacity. Not reproduced with no WM, fvwm, icewm, openbox, wmaker, xfwm4, mutter.
wm geometry . 400x300 does the same (8.4 too).
1. unix/tkUnixWm.c:ParseGeometry always sets WM_MOVE_PENDING, even for a size-only "WxH". UpdateGeometryInfo then sends XMoveResizeWindow with the frame position recorded from the WM. Metacity (invisible borders) interprets this differently, so the window moves.
2. library/ttk/sizegrip.tcl Drag re-applies +x+y from wm geometry, which has the same effect.
WxH. Verified under metacity (no move), fvwm and openbox. wm.test and unixWm.test give the same results before and after (only the no-WM baseline failures). No new test: it needs a reparenting WM with frame extents.
wm geometry . WxH (and the sizegrip, which re-sets +x+y) re-sends the frame position, and the WM moves the window. Fix: only move when a position is given, and make the sizegrip set only the size.
REPRODUCED (main, 8.6). RFE-like.
send app {return -code error -errorcode X -foo bar msg} gives code 1, the message, -errorcode and -errorinfo. The custom option -foo is lost, and -errorline/-errorstack are the local ones.
REPRODUCED (case 1, 9.1 main); case 2 NOT-REPRODUCED
., then wm deiconify of a withdrawn toplevel; it must end up above .. Case 2: raise . while a dialog holds the grab. Both checked with wm stackorder; prints PASS/FAIL and a VERDICT line.
wm deiconify of a withdrawn toplevel leaves it below . (stackorder .app1 .). Case 2: raise . above a dialog holding the grab is refused as expected (stackorder .d .).
Status now: Open
x11-menubar-height, not merged: Fix 2865578fff: X11: the toplevel shrank when its menubar was set again while it was going fullscreen or zoomed. The size requested for the toplevel was compux11-menubar-height, not merged: Fix 2865578fff: X11: the toplevel shrank when its menubar was set again while it was going fullscreen or zoomed. The size requested for the toplevel was compuREPRODUCED (main, 8.6, 8.5)
update between steps: icewm leaves the window at 1280x955 (main)/1280x961 (8.6) instead of 40x24; openbox/fvwm OK. Without update (the ticket's sample): openbox gives 40x1 or 40x52, fvwm 40x-10 (negative height from wm geometry), icewm 1280x1023 — timing dependent, all versions. Fullscreen-only or menu-only toggles are fine.
REPRODUCED (main, 8.6, 8.5)
wish script.tcl -h and wish -help on main, 8.6, 8.5 (Xvfb): prints "application-specific initialization failed: Command-specific options: ..." and then continues: the script runs without Tk ("package Tk is not present") or the interactive shell starts; exit status 0 for wish -help </dev/null.
-h after the script name also matches because wish parses all of argv unless -- is used. Separately, Tk_ParseArgv still ignores TK_ARGV_NO_DEFAULTS when matching (nijtmans' 2009 patch never applied), though Tk no longer uses it for init.
(int)(x + 0.5) in the angled-t…REPRODUCED (main, 8.6); not in 8.5/8.4. Introduced by 9dc3d444b7 (2008-11-22, patthoyts: replaced C99 round() with (int)(x + 0.5) in the angled-text TextToArea).
.c find overlapping 0 0 99 300 returns the text item at x=100 on main/8.6, not on 8.5/8.4; top edge not affected in the ticket example but same code.
(int) ((rectPtr[0] + 0.5) - textPtr->drawOrigin[0]) truncates toward zero for negative values (-99.5 -> -99 instead of -100), shifting the area one pixel right/down when it starts left/above the text origin. Tk_IntersectTextLayout's comparisons are fine (8.5 semantics restored without touching them).
find overlapping 0 0 99 300 finds the text at x=100 / after it does not
REPRODUCED (main, 8.6) (by code and a partial run). Really an RFE.
selection handle -type image/png -format image/png with a handler returning "0x89 0x50 ..."; another Tk client reads it back as 32-bit values. xclip/xwd are not installed, so the property format was checked in the code)
char * chunks (INCR code uses strlen), so raw bytes cannot be carried either. Retrieval already handles format 8 (SelCvtFromX8).
Status now: Open
x11-wm-manage-no-flicker, in main, 9.0: Fix 2817531fff: "wm manage" is deficient and flickering.trunk, in main, 9.0: Fix for 2817531fff: "wm manage" is deficient and flickeringcore-9-0-branch, in main, 9.0, 8.6: Fix for 2817531fff: "wm manage" is deficient and flickeringcore-8-6-branch, in 8.6: Fix for 2817531fff: "wm manage" is deficient and flickeringREPRODUCED (main, 8.6, 8.5)
wm manage .f; wm withdraw .f still maps the new wrapper at +0+0 and unmaps it again at once (flicker). The frame gets Map/Unmap events.
wm overrideredirect $w has no value, so it is only a query. With the fix, wm manage; wm withdraw; wm overrideredirect 1; wm geometry; wm deiconify maps once, override-redirect, at the right place.
REPRODUCED (9.1 main, 8.6 tip)
!(tmPitchAndFamily & TMPF_VECTOR)), it creates the same LOGFONT with OUT_TT_ONLY_PRECIS and the raster font's pitch and family (Courier gives Courier New), and draws the run's characters with ExtTextOutW. The lpDx widths are summed from the shaped glyph advances through logClust, so the text length matches Tk's measurement. RTL runs and TrueType fonts take the old path unchanged. Bbox padding is not included: 9fd94c63b0's redraw margin already covers the remaining 1–2 px TrueType rounding and the slightly wider substitute glyphs. The patch is independent of 3249f7d4c6.patch: both apply on top of each other in either order, since 3249 only changes FamilyExists/WinFontExistProc and winfont-2.8/13.1. 2816150fff.patch (101 changed lines: 69 in tkWinFont.c, of which about 25 are the function header and declaration, plus 32 test lines. That is over the 60-line guideline.)
REPRODUCED (main, 8.6, 8.5)
wm iconphoto . -default p, and a new toplevel in the parent interp then gets _NET_WM_ICON (checked with xprop).
-default sets the icon of the shared window class (SetClassLongPtrW), which is process-wide.
interp delete.
make clean first (Tk's Makefile does not track tkInt.h, and a partial rebuild segfaults in the tests).
Status now: Closed (Duplicate)
REPRODUCED (main, 9.0, 8.6). Regression since 8.5 (b12f6d6484, 2007-11-02, "file chooser now uses Ttk widgets")
REPRODUCED (9.1 main, 8.6 tip)
-multiple 1 -initialfile {a.txt {b c.txt}} the entry shows the list, and pressing OK returns both files, so the list semantics work. Repro script: win/2473895fff.tcl (the user just presses Open).
"a" "b" form when -multiple is set (options can come in any order, so this must happen after parsing). macosx/tkMacOSXDialog.c (OPEN_INITFILE) also uses the string as one file name.
a.txt {b c.txt} verbatim; pressing Open brings up an error box, and the dialog never returns. With the prototype the box shows "a.txt" "b c.txt" and the result is both files.
initFileObj = valuePtr;, so the last -initialfile wins and the result is converted once after the loop.
a.txt {b c.txt} / after: "a.txt" "b c.txt"
REPRODUCED (main, by code inspection). The PNG reader ignores the gAMA chunk: generic/tkImgPNG.c lists CHUNK_gAMA among the "not used by this implementation" ancillary chunks. The photo's -gamma option is applied only at display time, the same way for every format.
1 1 2 1 instead of 1 1 2 2. This is a duplicate of af31a84c91.REPRODUCED (main, 9.0, 8.6, 8.5, 8.4). Result is 1 1 2 1 instead of 1 1 2 2. This is a duplicate of af31a84c91.
1 1 2 2 and select.test passes (97 passed, 0 failed). I then reverted it. The old branch bug-2443069 (2012) was reverted from trunk because of [3543050]; since then the current code copies CommandInfo per handler.
Status now: Closed (Fixed)
core-8-6-branch, in main, 9.0, 8.6: Fix 2358545fff (again). Thanks, Serhiy!spinbox-octal-86, in main, 9.0, 8.6: Fix the bug reference in the spinbox-26.2 test title. [Bug 9e89324a0a]REGRESSED on 8.6 tip. dgp fixed it in 8.5.10 (Tcl_GetDouble replaced by sscanf("%lf")). Check-in e0dd3fdb59 (2026-09-22, core-8-6-branch, "Fix 9e89324a0a: spinbox parsing depends on the LC_NUMERIC locale") switched back to Tcl_GetDouble, so the octal problem is back on 8.6: with -format %02.0f the value goes 07 → 08 → 00. It is also silently wrong: "010" is read as 8. main and 9.x are not affected because Tcl 9 has no octal parsing.
06 07 08 00 01 02 11 10 09 00 00. 8.6.15, 8.6.13, 8.6.8, 8.5.19 and 8.4 OK.
Status now: Closed (Fixed)
x11-grab-unviewable-button, in main, 9.0: Fix [2182522]: Ttk combobox fails to restore grab. A local grab made while a mouse button is down is turned into a temporary global grab, which fails if the wintrunk, in main, 9.0: Fix for [2182522]: Ttk combobox fails to restore grab.core-9-0-branch, in main, 9.0, 8.6: Fix for [2182522]: Ttk combobox fails to restore grab.core-8-6-branch, in main, 9.0, 8.6: Fix for [2182522]: Ttk combobox fails to restore grab.REPRODUCED (main, 8.6, 8.5)
grab current is empty and top2's Quit works. With a quick click (release before the Unmap is processed) the grab is restored, so the bug depends on timing.
Buildrequires: XFree86-develREPRODUCED (main, 8.6): unix/tk.spec still has Buildrequires: XFree86-devel
REPRODUCED (main, 8.6, 8.5)
-anchor center to TMenubutton in classic and vista to keep their centered text; the default layout already anchors w. Aqua was left unchanged. The new test fails without the fix, and all ttk tests pass.
pack -fill x versions are pixel-identical before and after in all four themes. Only the -width 1 + -fill x case changes (the label is no longer clipped).
ttk::menubutton .a -text Hello at natural size, packed -fill x (the vista text must stay centered, winnative left), and -width 1 with -fill x (the text must not be clipped). Under vista, also check that the dropdown arrow is unchanged.
identify element in the middle of a -width 1 menubutton gives padding with both the default and the vista theme / after: label
vista); fail before: yes; pass after: yes
testConstraint vista. layout-3.2 restores the theme. layout-3.1 still leaves the theme at "default" (harmless in this file).
REPRODUCED (main, 8.6, 8.5). This is intended behaviour, but it is not documented, so it is a DOCS issue.
ttk::clickToFocus, which checks ttk::takesFocus, i.e. -takefocus (library/ttk/utils.tcl). TCheckbutton and TRadiobutton copy this binding.
f436621c1a REPRODUCED (9.1 main, 8.6 tip), prototype verified. 2045553fff REPRODUCED ("" and absent differ); doc prototype verified and extended.
-defaultextension "" + -filetypes {{xyz *.xyz}} the result is myfile.xyz. With the option absent it is also myfile.xyz. With .abc it is myfile.abc.
foo (case 1), and also foo after switching to Text (case 2). -defaultextension "" gives the type's extension (foo.tcl, or foo.txt with Text selected). 2045 script: "" gives myfile.xyz, absent gives myfile.
-defaultextension .dat with first type {"All files" *} gives foo.dat; with first type {Text .txt} gives foo.txt; with {"Tcl or Text" {.tcl .txt}} gives foo.tcl. On Windows the extension of the selected type wins over -defaultextension (on Unix an explicit -defaultextension wins, see tkfbox.tcl SetFilter).
foo.tcl, case 2 foo.txt (follows the type selector). 2045 script: both give myfile.xyz. The dx.tcl results do not change.
SetDefaultExtension(L"") (7 code lines), replacing the earlier filter-parsing version. It includes getOpenFile.n text for the patched behaviour and the two tests. 2045553fff.patch (doc only, for unpatched behaviour) is updated with the rule that the selected type's extension wins on Windows. Use one of the two doc texts, depending on whether f436 goes in.
Status now: Closed (Fixed)
toolbutton-center, in main, 9.0: Fix [1867834]: ttk Toolbutton has wrong default anchor. The text of a Toolbutton is centered in all built-in themes, as for TButton and for Toolbutton in the cltrunk, in main, 9.0, 8.6: Fix for 1867834fff: ttk Toolbutton has wrong default anchor.core-9-0-branch, in main, 9.0: Fix for 1867834fff: ttk Toolbutton has wrong default anchor.core-8-6-branch, in main, 9.0, 8.6: Fix for 1867834fff: ttk Toolbutton has wrong default anchor.REPRODUCED (main, 8.6, 8.5)
ttk::style lookup Toolbutton -anchor is empty in the default, alt and classic themes and "center" only in clam (and aqua). A screen grab of a -width 10 Toolbutton in the default theme shows 6px left / 50px right text margins; in clam it is 30/28.
-anchor center in each theme, but Toolbutton only does so in clam/aqua. Style settings do not inherit across parent themes, so every theme needs it.
-anchor center for Toolbutton in defaults/alt/classic/winTheme/vistaTheme.tcl; new test ttk-16.3 in tests/ttk/ttk.test fails before and passes after; ttk.test passes 111/111). For 8.6, xpTheme.tcl also needs it. This slightly changes behaviour for apps that give a Toolbutton an explicit width.
-anchor center only in clam/aqua, so the label falls back to the element default "w". Fix: set -anchor center for Toolbutton in every theme, as TButton already does (test ttk-16.3).
REPRODUCED (main, 8.6). Still true, but this is a cleanup decision rather than a bug.
testfont subfonts works on the main tktest build (it lists the fontconfig fallback fonts). No test in tests/ uses it. TkpGetSubFonts is still internal stub slot 110 and is implemented in tkUnixFont.c, tkUnixRFont.c, tkUnixBidiFont.c (newly added), tkWinFont.c and tkMacOSXFont.c.
testfont subfonts still works and is a useful debugging aid (it was even implemented in the new tkUnixBidiFont.c). Suggest keeping it and closing as Won't Fix. Alternatively, add a smoke test that calls it.
REPRODUCED (main, 8.6): the tests still compare case-sensitively. unixfont-2.9 was already removed on main/9.0 in 186f54c998/73db542952 (Bug 4eb4c07dae) but is still present in 8.6.
font actual {-family fixed} gives "Fixed". The haveFixedFamilyFont constraint lowercases the name, so it passes, while unixfont-2.6/2.8 compare exactly against "fixed" and fail.
string tolower but the tests do not.
string tolower in unixfont-2.6 and 2.8; they fail before and pass after in the reproduced setup). For 8.6 the same change is needed, plus 2.9 (or backport its removal).
Notes: the checkout was reconfigured against tcl9.1. It is reverted on main b56b1a051f with no changes left. The untracked doc/man.macros-original was already there. Xvfb :111 (my PID) is stopped. The modified patches are 03fcf233e1, 1158738fff, 1600dc73a9, 1d926db566 and 1f1273f739; the originals are kept as <id>.patch.1024. During the session a fossil diff without -i once failed with "gdiff-command: not found" and produced nothing (the patch was redone with fossil diff -i); all saved patches were made with the internal diff.
REPRODUCED (main, 8.6)
yview scroll 25 units takes about 300 ms per step, compared with 2.5 ms for xview scroll. Main is about 1.4x slower than 8.6 here.
Status now: Closed (Fixed)
menu-clone-cascade-destroy, in main, 9.0: Merge trunk. Renumber the test for [1723059] to menu-45.1, since trunk now has another menu-42.1.trunk, in main, 9.0: Fix for 1723059fff: entryconfigure destroys submenuscore-9-0-branch, in main, 9.0, 8.6: Fix for 1723059fff: entryconfigure destroys submenuscore-8-6-branch, in 8.6: Fix for 1723059fff: entryconfigure destroys submenusREPRODUCED (main fb166f9f73, 9.0.5, 8.6.18, 8.5.19, 8.4.20). Fixed on branch menu-clone-cascade-destroy (ef4c358706 2026-09-23, merged with trunk in 257a67c1c0 2026-09-30, test menu-45.1), not merged to main.
Status now: Open
REPRODUCED (main, 8.6, 8.4)
*background: stupid, *borderWidth: abc, *relief: bogus, *cursor: nosuchcursor and *highlightThickness: x make wish fail at startup ("application-specific initialization failed: …") on 9.1b1 and 8.6.18. 8.4.20 prints the exact message from the report. *foreground: stupid and *font: {nosuch let wish start, but most widgets then fail to create. *Text.tabs: {1c q} breaks text in 9.1 only.
option add, but Tk_GetOption does not return the priority.
-background {} are not transparent.REPRODUCED (main, 8.6, 8.4). This is by design: frames with -background {} are not transparent.
destroy .c.f2.f1, the padding area of .c.f2 (bg {}) keeps stale cyan pixels instead of the canvas red. The result is the same on main, 8.6 and 8.4.20.
-background does not make the widget transparent and that uncovered areas may show stale contents.
-background gives the window a None background, so Tk never repaints it. Real transparency is not possible there. Proposed documenting this in frame.n/toplevel.n and closing.
Status now: Closed (Fixed)
option-stack-realloc, in main, 9.0: Fix [1652598]: Free memory read tkOption.c SetupStackstrunk, in main, 9.0: Fix for [1652598]: Free memory read by SetupStacks in tkOption.c.core-9-0-branch, in main, 9.0, 8.6: Fix for [1652598]: Free memory read by SetupStacks in tkOption.c.core-8-6-branch, in main, 9.0, 8.6: Fix for [1652598]: Free memory read by SetupStacks in tkOption.c.REPRODUCED (main; the same code is in 8.6 and 8.4)
option add *f*gN.foo for N up to 2000, followed by *zz*q.foo, creating .f makes ExtendStacks() reallocate the WILDCARD_NODE_NAME stack while SetupStacks() still loops over it with elPtr ("DANGLING stack 6 remaining 1"). valgrind does not flag it because Tcl's allocator caches the freed blocks.
tsdPtr->stacks[i]->els with a pointer. ExtendStacks() → ExtendArray() can Tcl_Realloc that same stack (a wildcard node's children are appended to the same wildcard stack), which leaves elPtr dangling.
elPtr after each ExtendStacks() call, which is essentially the reporter's suggestion. Test option-17.1 added. option.test passes (105/105).
elPtr dangles. The fix is to iterate by index.
Status now: Closed (Fixed)
menu-post-under-pointer, in main, 9.0: Fix [470331], [680660], 1596662fff, f9d316a5e0: a menu posted over its menubutton or menubar entry invoked the entry under the pointer on the release of thetrunk, in main, 9.0: Fix for 470331ffff: Displaced menus do not stay open; 680660ffff: Menu items accidentally selected; 1596662fff: Menu behaviour at screen bottom; [f9d316a5core-9-0-branch, in main, 9.0, 8.6: Fix for 470331ffff: Displaced menus do not stay open; 680660ffff: Menu items accidentally selected; 1596662fff: Menu behaviour at screen bottom; [f9d316a5core-8-6-branch, in main, 9.0, 8.6: Fix for 470331ffff: Displaced menus do not stay open; 680660ffff: Menu items accidentally selected; 1596662fff: Menu behaviour at screen bottom; [f9d316a5menu-post-under-pointer, in main, 9.0: Add a widget demo for popup (context) menus posted with tk_popup, with menus of different sizes.REPRODUCED (main, 8.6, 8.4). This is a duplicate of f9d316a5e0 ("linux menu problem if menu near the bottom of screen").
-direction below fallback in library/menu.tcl also uses a wrong formula.
REPRODUCED (main, 8.6)
xsel -o -p plus a second wish that requests UTF8_STRING and STRING. Results for the ticket's cases: I (replace text's STRING handler) gives ????. II and IV (selection handle -type UTF8_STRING) give ????. V works. A STRING request returning ???? is correct per the ICCCM (Latin-1), as dkf said.
selection handle -type UTF8_STRING with no -format defaults the format to STRING, so tkUnixSelect.c ConvertSelection encodes the data as iso8859-1.
-type is UTF8_STRING and no -format is given, the format now defaults to UTF8_STRING, and selection.n says so. Together with af31a84c91.patch, xsel gets "тест" in cases I, II, IV and V. select.test (96 passed) and clipboard.test pass. select-14.4 fails without the fix.
selection handle -type UTF8_STRING also defaulted to -format STRING and so sent Latin-1. There is a prototype fix for both.
????) / after "тест"
tk scaling 2.0, a posted WM_DISPLAYCHANGE (same depth and size) resets it to 1.3317.REPRODUCED (9.1 main, 8.6 tip): after tk scaling 2.0, a posted WM_DISPLAYCHANGE (same depth and size) resets it to 1.3317.
tk scaling 2.0 survives update and a 1.5 s after.
tk scaling is stored in WidthMMOfScreen/HeightMMOfScreen. On Aqua, TkMacOSXDisplayChanged overwrote them (it now does so only when they are 0). On Windows, the WM_DISPLAYCHANGE handler in win/tkWinWm.c (TkWinWmProc) recomputes WidthMMOfScreen/HeightMMOfScreen from LOGPIXELS, which silently resets a user-set scaling. The same "only if unset" approach or a saved user value would fix it.
tk scaling.
tk scaling 2.0, a posted WM_DISPLAYCHANGE (same depth and size) resets it to 1.3317.
tk scaling, because the screen mm size is recomputed from LOGPIXELS. Prototype: keep the current pixel/mm ratio on display changes; test winWm-11.1.
REPRODUCED (main, 8.6)
package require Tk, on Xvfb. After rename scale tk_scale; proc scale ...; destroy ., calling scale gives "application has been destroyed". Also found: rename canvas tk_canvas; destroy .; tk_canvas .c segfaults on main (valgrind: invalid read in Tk_NameToWindow). The renamed command keeps its now-freed main window as clientData.
destroy . crashes. That needs token-based tracking.
Notes: one slip during this batch. A wish8.5 started with the default DISPLAY=:0 ran for up to about 2 minutes, then I killed it. It only ran puts [info patchlevel] from stdin, with no input synthesis. All other runs used Xvfb :124, which has been stopped. wt-a4 is reverted and rebuilt on main. doc/man.macros-original is an untracked extra in wt-a4 that I did not create.
destroy . remains)
scale -> "application has been destroyed" / after scale -> "user scale"
isNativeObjectProc == 2 && objProc2 == cmdPtr->objProc check is right. USEINITPROC and SAVEUPDATECMD commands keep the old path.
REPRODUCED for the entry widget (main, 9.0, 8.6). For the text widget it is only partly fixed on main: the text widget has bidi layout there, but tagged RTL text is still scrambled (see 59d6d5f6c0).
REPRODUCED (main, 8.6)
wm resizable .t 0 0 then 1 1, after which the content grows to 480x500. Under mwm the window stays 200x150 on both main and 8.6 (2026-10-10). Without the toggle, mwm resizes it to 480x500. With no WM and with icewm, 480x500 is correct. twm needs interactive placement, so I could not test it.
wm maxsize call.
wm resizable 0 0 / 1 1 toggle triggers it, and an explicit wm maxsize avoids it. I suggest closing as Won't Fix (window manager quirk).
REPRODUCED (main, 9.0, 8.6, 8.5; the slowdown is much milder than the "tens of seconds" reported in 2015)
see end 0.09 s (8.6) / 0.17 s (main), so it is usable. Scaling is quadratic: see end N=200k 0.39 s/0.45 s, N=400k 1.85 s/2.2 s (8.6 / main non-bidi build). The installed main build with bidi is about 2x slower (IsSimpleOnly in unix/tkUnixBidiFont.c rescans the rest of the string). 8.4.20 is about 2.5x faster, with the same growth.
for (p = ... ; *p != 0; p++)) and MeasureChars's search for the next '\t'/'\n' are both O(rest of segment), and TkTextFindDisplayLineEnd/MeasureUp lay out from the start of the logical line. So one pass over a line of n chars costs O(n²/width).
see end) but takes about 2 s at 400k.
REPRODUCED (9.1 main, 8.6 tip)
Status now: Closed (Fixed)
REPRODUCED (main with bidi/HarfBuzz enabled, the default build); NOT-REPRODUCED on 9.0, 8.6, 8.5, 8.4 and on main built with --disable-bidi
.t bbox width with font measure for each character: 12 of 17 wrong on main (bidi build), 0 elsewhere. No WM.
.t2 never appears after both windows are deiconified (ismapped 0, no wrapper, owner 0). Ex2: …REPRODUCED (9.1 main, 8.6 tip), both examples. Ex1: .t2 never appears after both windows are deiconified (ismapped 0, no wrapper, owner 0). Ex2: .t2 appears, but GetWindow(GW_OWNER) is 0 instead of .t1's wrapper. Control (both mapped): the owner is correct.
wm transient is set while the container is unmapped and the transient is no longer WM_NEVER_MAPPED, both unix/tkUnixWm.c:WmTransientCmd and win/tkWinWm.c:WmTransientCmd only withdraw the transient. Neither sets the hint: XSetTransientForHint on X11, UpdateWrapper (the owner HWND) on Windows. Nothing sets it later when the window is deiconified. For the never-mapped case, TkWmMapWindow already sets it on X11 ([Bug 1163496]).
wm transient on a withdrawn window whose container is withdrawn never sets WM_TRANSIENT_FOR. Prototype fix for unix/tkUnixWm.c with test unixWm-37.6. win/tkWinWm.c has the same pattern (withdraws without UpdateWrapper) and needs a retest on Windows.
.t2 never appears after both windows are deiconified (ismapped 0, no wrapper, owner 0). Ex2: .t2 appears, but GetWindow(GW_OWNER) is 0 instead of .t1's wrapper. Control (both mapped): the owner is correct.
wm stackorder after raise .t1). Windows: the repro gives OK/OK with the correct owners. wm.test and winWm.test: 332 run, 0 failed. ref91 tktest fails 8.2 and 8.3. X11 (Linux wt-win, fvwm): 8.1–8.3 pass with the patch; without it 8.3 fails ({.t2 .t1}).
wm transient is set on a withdrawn window (X11 has the same example-2 bug). Prototype with tests wm-transient-8.2/8.3.
return; removal). The second win hunk (WmTransientCmd: withdraw, set initial_state Withdrawn, then always UpdateWrapper) still applies. Main also added its own wm-transient-8.2, so the patch's tests 8.2/8.3 became wm-transient-8.3/8.4.
{failsOnCILinux failsOnXQuartz} to withWindowManager, the same as 8.1: without a WM both failed even with the fix, because the stackorder is meaningless there.
Status now: Pending (Wont Fix)
REPRODUCED (Windows part, 9.1 main)
winfo rooty . = 174 and winfo rooty .#mb = 142, both one menubar height too low. Pulldowns are posted from these coordinates, so they open 31–32 px too low, which is the original report. A same-process container is not affected.
Tk_GetRootCoords(), branch for an embedded toplevel whose container is in another application. The loop has already added winPtr->changes.y (= menuHeight, the toplevel's offset in its wrapper). XTranslateCoordinates(winPtr->window → root) already includes that offset, so it is counted twice.
open "|[interpreter] … -use"). The test fails without the fix and passes with it; unixEmbed, unixWm, winfo, menu and unixMenu tests all pass. With the fix, menus post right under the embedded menubar.
Tk_GetRootCoords() adds the menubar height twice, so winfo rooty of the embedded toplevel and its menubar is off by the menubar height and pulldowns open too low. A fix with a test is ready. On Windows the menubar is missing because an embedded toplevel is a WS_CHILD window.
winfo rooty of the embedded toplevel and its menubar is one menubar height too low / after correct
vwait plus a 10 s safety timer, not a time delay, so I did not convert it to pause.
Status now: Closed (Fixed)
button-overrelief-after-click, in main, 9.0: Fix [1100518]: Button should stay in -overrelief state after eventtrunk, in main, 9.0, 8.6: Fix for 1100518fff: Button should stay in -overrelief state after event.core-9-0-branch, in main, 9.0: Fix for 1100518fff: Button should stay in -overrelief state after event.core-8-6-branch, in main, 9.0, 8.6: Fix for 1100518fff: Button should stay in -overrelief state after event.REPRODUCED (main, 8.6, 8.5, 8.4)
enter=raised press=sunken release=flat when release=raised is expected.
::tk::ButtonUp (all three variants: x11, win32, aqua). It always restores the cached -relief (Priv($w,relief)) and forgets the cache, even when the pointer is still over the button (Priv(window) eq $w).
-overrelief is set, ButtonUp switches to the overrelief and keeps the cached relief so that ButtonLeave can restore it later. New test button-16.1. button.test passes (414/415, 1 skipped). Also checked by hand: press, drag out and release gives flat. Press, drag out, drag back and release gives raised, then Leave gives flat.
REPRODUCED (main, 8.6). An unmerged fix branch already exists: bug-1096580fff (fvogel, last check-in 6c6755350a, 2017-02-07, tag soft-hyphen). I did not redo it.
-wrap word, Courier 12, text aaaaaaaa abcdefgh123456 in a 20-char widget. The second display line starts at 1.9, so there is no break at SHY. The SHY bbox is 10 px wide, the same as a full character.
REPRODUCED (9.1 main, 8.6 tip) for the 1-px endpoint mismatch. The small-extent arcs are no longer full circles (fixed part confirmed).
REPRODUCED (9.1 main, 8.6 tip): offset 0 and offset 8 give identical captures at widths 1 and 3. The dash lengths are also wrong: {8 8} is drawn as the stock PS_DASH pattern at width 1, and as dots at width 3.
111111111111111111000000... at width 1, dots at width 3) / after: {8 8} dashes are exact and rotated by -dashoffset, the same as X11
Status now: Closed (Fixed)
scroll-command-unmapped, in main, 9.0: Fix [991849]: removal/optimization of scrollbar events?trunk, in main, 9.0: Fix for 991849ffff: removal/optimization of scrollbar events?trunk, in main, 9.0: changes.md: Bug [991849]: new text: "canvas,text,ttk widgets: call scrollbar commands after window mapping (and not with 1x1 initial size)"core-9-0-branch, in main, 9.0, 8.6: Fix for 991849ffff: canvas,text,ttk widgets: call scrollbar commands after window mapping (and not with 1x1 initial size)core-8-6-branch, in main, 9.0, 8.6: Fix for 991849ffff: canvas,text,ttk widgets: call scrollbar commands after window mapping (and not with 1x1 initial size)REPRODUCED (main, 8.6, 8.4). This is closer to an RFE than a bug: the final callback is always correct.
canvas -xscrollcommand fires 0.002 0.002 while winfo width is 1 and winfo ismapped is 0, then fires the correct value after mapping. The text widget behaves the same way. Listbox and entry do not.
!Tk_IsMapped early exit jumps to done:, which still calls CanvasUpdateScrollbars with the 1x1 size the canvas has before geometry management.
xview/yview still return correct values. The text widget (tkTextDisp.c) would need a similar change, which is not done.
REPRODUCED (main)
#if !defined(_WIN32) && defined(NOT_YET)), so serhiy's test of 2026-09-23 still applies.
Status now: Open (Remind)
REPRODUCED (main, 8.6)
copy -to: 300x200 takes 0.25 s, 450x300 takes 1.6 s. 2.25× the pixels costs 6.4× the time, so the cost grows much faster than the image size. Both versions give the same numbers.
REPRODUCED (main, 8.6). This is a design limitation.
listbox -setgrid 1 -height 10 and a text widget are packed with -expand 1 -fill both. After wm geometry . 20x20, wm geometry reports 20x20 grid units, but the listbox only shows about 15 lines because the text widget takes part of the extra space.
Status now: Closed (Fixed)
cascade-grab-leave, in main, 9.0: Fix 873655ffff: missing <Leave> event when posting cascade menus.trunk, in main, 9.0, 8.6: Fix 873655ffff: missing <Leave> event when posting cascade menuscore-9-0-branch, in main, 9.0: Fix 873655ffff: missing <Leave> event when posting cascade menuscore-8-6-branch, in main, 9.0, 8.6: Fix 873655ffff: missing <Leave> event when posting cascade menusREPRODUCED (main, 8.6, 8.4)
<Leave> NotifyGrab and goes back to normal. With .m postcascade in the same command it gets no <Leave> and stays active.
grabWinPtr is already .m and .b is outside the grab tree. Probably the grab-change event is serviced while mapping .m.c waits for its map event. The restrict proc defers window events during that wait but not the grab-change event. I did not confirm this last step.
GENERATED_GRAB_EVENT_MAGIC. The new test fails without the fix and passes with it. grab, bind, event, menu, menubut, menuDraw, button, entry and unixEmbed tests pass. focus-2.6/2.7/2.9/5.1 and window-2.4..2.9 also fail on unpatched main, so they are not caused by this.
REPRODUCED (main, 8.6, 8.4)
-bd 10 and a 200x200 window item: the red child covers the canvas border at the right, the bottom and the corner. A text widget with -bd 10 and a 300px-wide embedded frame: the frame covers the right border on main.
event generate <KP_Enter> gives ?? with keycode 0.REPRODUCED (9.1 main): real keypad Enter (extended VK_RETURN) gives %K Return. event generate <KP_Enter> gives ?? with keycode 0.
event generate <KP_Enter> gets keycode 0. On X11 the new test (Return then KP_Enter) passes.
case VK_RETURN that checks EXTENDED_MASK.
<Return> bindings stop firing for keypad Enter on Windows, and Text/Entry insertion changes, because the library binds <KP_Enter> {# nothing}. That is the same behaviour X11 already has.
<Return> bindings.
event generate <KP_Enter> gives ?? with keycode 0.
key enter then ekey 0D into a focused text widget).
Return KP_Enter, and event generate <KP_Enter> gives KP_Enter, keycode 13. As on X11, keypad Enter no longer inserts a newline in text/entry (class binding <KP_Enter> {# nothing}). bind, key, winKey, entry, text and spinbox tests: 1878 run, 0 failed (bind-38.1 passes; the ref build fails it).
<Return> bindings no longer fire for the keypad key.
Return ?? / after: Return KP_Enter
no keycode for keysym "KP_Enter" (event generate -keysym KP_Enter); the repro also gives no newline. Windows has no KP_Enter keysym until 787402ffff (phase 1, bind-38.1) is applied. The patch is unchanged; commit it after 787402ffff, or give text-40.1 a constraint.
REPRODUCED (main fb166f9f73, 9.0.5, 8.6.18; both Xft and --disable-xft builds)
winfo id 0)REPRODUCED (9.1 main: 113 frames; 8.6 tip: 110 frames with winfo id 0)
TkpMakeWindow (win/tkWinWindow.c) doesn't check whether CreateWindowExW() returned NULL, so the extra widgets get a NULL HWND and draw through the desktop DC. That's why they show up in the top-left corner of the screen. At most Tk could report an error; it can't create more windows than the OS allows.
winfo id is 0)
winfo id 0)
menubutton and ttk::menubuttonStatus now: Closed (Fixed)
menu-post-under-pointer, in main, 9.0: Fix [470331], [680660], 1596662fff, f9d316a5e0: a menu posted over its menubutton or menubar entry invoked the entry under the pointer on the release of thetrunk, in main, 9.0: Fix for 470331ffff: Displaced menus do not stay open; 680660ffff: Menu items accidentally selected; 1596662fff: Menu behaviour at screen bottom; [f9d316a5core-9-0-branch, in main, 9.0, 8.6: Fix for 470331ffff: Displaced menus do not stay open; 680660ffff: Menu items accidentally selected; 1596662fff: Menu behaviour at screen bottom; [f9d316a5core-8-6-branch, in main, 9.0, 8.6: Fix for 470331ffff: Displaced menus do not stay open; 680660ffff: Menu items accidentally selected; 1596662fff: Menu behaviour at screen bottom; [f9d316a5menu-post-under-pointer, in main, 9.0: Add a widget demo for popup (context) menus posted with tk_popup, with menus of different sizes.REPRODUCED (main, 8.6, 8.4), both menubutton and ttk::menubutton
tk::MenuInvoke. The ButtonRelease of the click that posted the menu goes to the menu when the menu is under the pointer, and gets treated as a selection.
MbPost (when posting from a button press) and ttk Pulldown save the pointer position in Priv(postPointer). MenuInvoke ignores the first release if the pointer hasn't moved (less than 3 px) and keeps the menu posted; for ttk it calls TransferGrab. MenuUnpost and MbButtonUp clear the value. Checked: click, move, click works for big and small menus, for Tk and ttk; press-drag-release still selects. menu.test and menubut.test pass; the new tests fail without the fix. Side effect: a quick click on a tk_optionMenu now leaves the menu posted instead of re-selecting the current value.
REPRODUCED (main, 8.6)
tk_getOpenFile -initialdir d -initialfile b.txt on main and 8.6.18: the entry shows b.txt but no icon is selected. The multi-file part of the request (-initialfile as a list) was rejected by dkf; see TIP 141.
::tk::dialog::file::Update fills the icon list but never selects data(selectFile).
data(selectFile), sets the anchor and scrolls it into view. filebox.test and choosedir.test pass; the new test fails without the fix.
after 100 because the dialog is modal: the check has to run inside the dialog's event loop, the same way ToPressButton does, so pause cannot be used here.
REPRODUCED (main, 8.6, 8.5)
tk::Priv(postedMb) still names the old .mb, so tk::MbPost returns early).
tk::Priv(postedMb) when the posted menubutton is destroyed, and tk::MbPost returns early when $w eq $Priv(postedMb).
bind Menubutton <Destroy> class binding that resets Priv(postedMb) and restores Priv(focus). menubut.test passes; the new test fails without the fix.
-constraints x11. With that, menubut.test is 118/0 (15.1 skipped). The <Destroy> binding was not checked on Windows.
Status now: Closed (Fixed)
trunk, in main, 9.0: Fix [600313]: the icon list of the file dialog no longer clears the selection when it loses focuscore-9-0-branch, in main, 9.0: Fix [600313]: the icon list of the file dialog no longer clears the selection when it loses focusiconlist-keep-selection, in main, 9.0: Shift-double-click in the icon list no longer invokes the file dialog. Add a test for mixed Control-click and Shift-click.REPRODUCED (main, 8.6). Only the FocusOut item is left open; dkf fixed the others in 2005.
focus -force another toplevel. The icon-list selection is cleared (the entry keeps the names). A later Ctrl-click then starts a new selection, so the earlier picks are lost. The same happens when a focus-follows-mouse WM moves focus away.
method FocusOut always does $w selection clear 0 end, even when focus leaves the dialog's toplevel entirely.
Status now: Closed (Fixed)
trunk, in main, 9.0: Fix 546607ffff: Do not reset the cursor over a window not managed by Tkcore-9-0-branch, in main, 9.0, 8.6: Fix 546607ffff: Do not reset the cursor over a window not managed by Tkcore-8-6-branch, in 8.6: Fix 546607ffff: Do not reset the cursor over a window not managed by Tkwin-foreign-cursor, in main, 9.0: Do not reset the cursor over a window not managed by Tk.REPRODUCED (9.1 main); FIXED on branch win-foreign-cursor (manual check)
Status now: Pending (Works for Me)
REPRODUCED on X11 (main, 9.0, 8.6, 8.5, 8.4) with eserte's example (grab set in the <ButtonPress-1> binding). The original Windows case (grab set before the press) is not reproduced: serhiy on Win11, and on X11 it goes through Note 6.
grab current is still "."; the ButtonRelease goes to "." (bind . <ButtonRelease-1> sees it at 598,571).
REPRODUCED (main, 8.6, 8.4)
Wish.geometry: 400x300+100+50 loaded by xrdb on Xvfb and wish -name wish, option get . geometry Geometry returns 400x300+100+50 but wm geometry . is 200x200+0+0 on main, 8.6 and 8.4.20.
-geometry command line option and never looks up the geometry resource of the main window as Xt apps do.
-geometry was not given, Tk_GetOption(main, "geometry", "Geometry") is applied with wm geometry .; invalid values are ignored. Verified: the resource is honoured, -geometry still wins, and a bogus value is ignored. wm.test has the same 10 no-WM failures as without the patch. This is a behaviour change, since users with *geometry resources will see wish follow them, so it may need discussion or a TIP.
Wish.geometry: 400x300+100+50 loaded by xrdb (an xprop client kept Xvfb from resetting) and -name wish: before 200x200+0+0 / after 400x300+100+50. With -geometry 300x200+10+10 the command line wins (300x200+10+10). A bogus resource is ignored (200x200+0+0).
*geometry resources set, so it may need discussion.
package require Tk without DISPLAY fails with "no display name and no $DISPLAY environment variable". This is by design, and T…REPRODUCED (main): package require Tk without DISPLAY fails with "no display name and no $DISPLAY environment variable". This is by design, and Tk ships a hand-written pkgIndex.tcl.
Status now: Closed (Fixed)
font-multiple-displays, in main, 9.0: Fix [483387]: BadFont error when a named font used on another display was changed or recreated. The fonts which depend on a named font were recreated for the ditrunk, in main, 9.0: Fix [483387]: BadFont error when a named font used on another display was changed or recreatedcore-9-0-branch, in main, 9.0, 8.6: Fix [483387]: BadFont error when a named font used on another display was changed or recreatedcore-8-6-branch, in main, 9.0, 8.6: Fix [483387]: BadFont error when a named font used on another display was changed or recreatedREPRODUCED (main, by instrumentation; the code path is the same in 8.6/8.5/8.4). No X error is visible here because only one X server is available: a second connection to the same server via -screen unix/:122.0 shares the XIDs, which hides the error.
-screen :122.1 and unix/:122.0; no X error. With a temporary check in Tk_DrawChars on main, fontPtr->display != display fires twice after font delete; font create, and does not fire with the fix.
font create/configure. Instances allocated for another screen/display are therefore reopened on the wrong display (wrong font XID/XftFont and wrong DPI), which gives BadFont on a real second server. font configure of a named font takes the same path.
fontPtr->screen (falling back to tkwin) and passes it to TkpGetFontFromAttributes. font.test passes.
Status now: Closed (Fixed)
win-mono-image, in main, 9.0: Fix [481255]: photo images with -palette 2 were corrupted on Windows. TkAlignImageData() computed the line length of the output bitmap from the line length of twin-mono-image, in main, 9.0: Add test imgPhInstance-7.3: -palette 2 draws black and white pixels in place [481255].trunk, in main, 9.0: Fix [481255]: photo images with -palette 2 were corrupted on Windowscore-9-0-branch, in main, 9.0, 8.6: Fix [481255]: photo images with -palette 2 were corrupted on Windowscore-8-6-branch, in 8.6: Fix [481255]: photo images with -palette 2 were corrupted on Windowswin-mono-image, in main, 9.0: Rebase to mainwin-photo-gamma-palette, in main, 9.0: Add tests imgPhInstance-7.1 and 7.2 for -gamma and -palette 32f2e19de8.REPRODUCED (8.6 tip): the -palette 2 row is inverted and scrambled (wrong line stride). 9.1 main: not visible, because since the main merge 3bbe54bc74 (2026-06-15) win/tkWinPort.h defines TK_CAN_RENDER_RGBA, and photos are drawn from pix32. -palette therefore has no visible effect on Windows in 9.1: p2 shows the smooth grey ramp.
-palette 2 photo with stripes, width 101, read back from the screen matches the source pixel for pixel. Windows repro: win/481255ffff.tcl (visual check; the window text explains PASS/FAIL).
bitmap_bit_order = LSBFirst in win/tkWinImage.c XCreateImage) is still in place. There is a likely second problem in win/tkWinDraw.c TkPutImage(), in the 1-bit branch. It sets SetTextColor(fg)/SetBkColor(bg), but when Windows blits a monochrome bitmap to a colour DC, 0 bits get the text colour and 1 bits the background colour. That is the opposite of X, so the photo would be drawn as a negative. XCopyPlane in the same file already swaps the two colours ("seems backwards"). Only photos use the 1-bit path on a colour display: palette 2, or the fallback when the colormap is full.
-palette 2 photos inverted. Candidate fix: swap them, as XCopyPlane already does. Needs checking on Windows.
#undef TK_CAN_RENDER_RGBA in tkImgPhInstance.c. The colour swap alone fixes the inversion, but the stripes stay scrambled. With the second fix, p2 is correct: black block, stripes, dithered ramp.
dataWidth = (image->width + 7) / 8 in TkAlignImageData. Bitmaps (-bitmap, bitmap image, canvas bitmap) are pixel-identical to ref91. imgPhoto, imgBmap, bitmap, winDraw, canvImg, image, button, canvas and menu tests: 1574 run, 0 failed (without the test hack). Relevant for 8.6/9.0; on 9.1 the path is only used without TK_CAN_RENDER_RGBA.
-palette 2 photos are drawn inverted and with shifted lines. Two causes: TkPutImage sets fg/bg the X way round, and TkAlignImageData keeps the 32-bit line padding that CreateBitmap doesn't expect. Prototype fixes both. In 9.1, Windows draws photos from RGBA, so -palette no longer affects the display there.
Status now: Closed (Fixed)
menu-post-under-pointer, in main, 9.0: Fix [470331], [680660], 1596662fff, f9d316a5e0: a menu posted over its menubutton or menubar entry invoked the entry under the pointer on the release of thetrunk, in main, 9.0: Fix for 470331ffff: Displaced menus do not stay open; 680660ffff: Menu items accidentally selected; 1596662fff: Menu behaviour at screen bottom; [f9d316a5core-9-0-branch, in main, 9.0, 8.6: Fix for 470331ffff: Displaced menus do not stay open; 680660ffff: Menu items accidentally selected; 1596662fff: Menu behaviour at screen bottom; [f9d316a5core-8-6-branch, in main, 9.0, 8.6: Fix for 470331ffff: Displaced menus do not stay open; 680660ffff: Menu items accidentally selected; 1596662fff: Menu behaviour at screen bottom; [f9d316a5REPRODUCED (main, 8.6, 8.5)
event generate on main/8.6/8.5, and a real XTEST click confirmed it on main. The menu is shifted up under the pointer, the release invokes "Item 8" and the menu unposts.
bind Menu <ButtonRelease> calls tk::MenuInvoke without checking whether the pointer moved since the press that posted the menu.
<Button-1> binding record the press window and root position. A new tk::MenuButtonUp ignores a release in a different menu within 2 px of the press, so the menu stays posted. After the patch the menu stays open; a second click on an item invokes it; a press-drag-release still invokes. menu/menubut/menuDraw/unixMenu tests pass. No test added because it needs screen-edge placement.
Status now: Open
REPRODUCED (main, 8.6, 8.4)
font actual {times -12} and {times -13} both give -size 9, while reqwidth (8.6: 40 vs 43) and linespace (13 vs 14) differ.
font actual turns the actual pixel size into points and rounds to an integer ((int)(size + 0.5)). 12 px = 8.64 pt and 13 px = 9.36 pt both round to 9. fa.size is a double internally.
font actual rounds the size to whole points, so -12 and -13 px both show as 9 pt at 100 dpi. Fixing it means reporting fractional points or pixels.
REPRODUCED (9.1 main, 8.6 tip)
pack -anchor ...; update idletasks) found no stale button pixels; a sanity run confirmed that the check detects the button.
after 700. The red area grows from 1.7 to 7.4 button areas. The final shot shows 9 red "Hello World!" copies (one at each anchor) on the blue background.
update idletasks processes neither the message nor the window event, and WM_ERASEBKGND does nothing (tkWinX.c: result 0). On X11 the server repaints the window background by itself, so the problem does not show there. It is not a flushing problem (the 3017005 check shows GDI output appears at once), so a GdiFlush in XSync would not help.
update idletasks. That is a behaviour change, and there is a flicker risk.
update idletasks does not process. X11 is unaffected because the X server paints window backgrounds.
Status now: Pending (Fixed)
win-canvas-arc-stipple, in main, 9.0: Fix [220787]: Stipple patterns don't work in arc/oval items on Windowstrunk, in main, 9.0: Fix [220787]: Stipple patterns don't work in arc/oval items on Windowstrunk, in main, 9.0: Stipple tests canvas-27.1, canvas-27.2 and canvRect-13.1 to 13.3 (from [220787]) fail on Aqua, which does not support stippling: add the notAqua constraint.core-9-0-branch, in main, 9.0: Fix [220787]: Stipple patterns don't work in arc/oval items on Windowswin-canvas-arc-stipple, in main, 9.0: Update changes.mdREPRODUCED (9.1 main); FIXED on branch win-canvas-arc-stipple
Status now: Closed (Fixed)
trunk, in main, 9.0: Fix [220796]: -stipple option for canvas text item disrupts positioning. Testcase now complete yettrunk, in main, 9.0: canvText-21.1 (bug [220796]): the text, given in points, did not fit in the 200x60 canvas at a high screen resolution, so countPixels read outside of the canvaswin-text-stipple-9.0, in main, 9.0: Fix 220796ffff for 9.0: -stipple option for canvas text item disrupts positioning on Windows. Stippled text was not drawn, and angled stippled text was misplacore-9-0-branch, in main, 9.0, 8.6: Fix [220796]: -stipple option for canvas text item disrupts positioningcore-8-6-branch, in 8.6: Fix [220796]: -stipple option for canvas text item disrupts positioningwin-text-stipple, in main, 9.0: Merge main.tests-min-width, in main: Test textDisp-33.3 failed on Windows when the 480 pixel wide frame .f and the 80-column text widget were wider than the screen: the text widget was laid out a sREPRODUCED (9.1 main); FIXED on branch win-text-stipple
Status now: Closed (Fixed)
trunk, in main, 9.0, 8.6: Fix [220895]: Canvas inconsistently draws lines on Windowscore-9-0-branch, in main, 9.0: Fix [220895]: Canvas inconsistently draws lines on Windowscore-8-6-branch, in 8.6: Fix [220895]: Canvas inconsistently draws lines on Windowswin-thin-line-endpoints, in main, 9.0: Merge main. Main moved stippled drawing into RenderStippled(): the last point of a thin polyline is now also drawn in DrawPathProc().REPRODUCED (9.1 main); FIXED on branch win-thin-line-endpoints
Status now: Open
x11-coords-to-window, in main: Fix 586f722cdd and 220856ffff in Tk_CoordsToWindow() on X11. A toplevel that was just withdrawn was still found while the window manager had not yet unmappeREPRODUCED (main, 9.1, 8.6 tip, 8.6.10+, and partly 8.6.9, 8.6.8, 8.4.20). This contradicts the 2026-09-23 comment, which could not test a virtual root.
__SWM_VROOT, reparents Tk's wrappers into it, sets __SWM_ROOT on the wrappers and sends ICCCM synthetic ConfigureNotify. Three modes, probing points in ., in .t and on the desktop:
'' for both toplevels).
.t; 8.6 tip and main find neither.
Tk_CoordsToWindow(), the child == wmPtr->reparent case, has two problems:
PointInWindow(x, y, …) with coordinates relative to the previous level (the real root) rather than childX/childY (relative to the vroot, like winPtr->changes). This regression came with 359434f369 / 6942f5af38 (2019-01-04, fix for 18a4ba19bd), first released in 8.6.10.
childX/childY, and when the point is not in that toplevel it goes on with the other toplevels and then descends into the frame; title-bar points still give ''. Checked in all three modes, including a title-bar point, and with twm/fvwm/icewm; unixWm.test and winfo.test pass. No automated test: one needs an external reparenting client. The emulator could become a testvroot command if wanted.
winfo containing returns "" for any toplevel inside a decoration frame inside a virtual root, because Tk_CoordsToWindow() checks the point with coordinates relative to the wrong window. In all versions it also fails when the WM puts several toplevels into one frame. A small fix is ready.
Status now: Closed (Fixed)
tk8-mode-tcl-size, in main, 9.0: Fix 22d2341c9d: Building extensions for Tk 8 and Tcl 8 in a Tcl 9 environment. Since the fix for Tcl ticket ad08bca6b1 (Tcl 9.0.4), tcl.h undefines Tcl_Size acore-9-0-branch, in main, 9.0: Fix 22d2341c9d: Building extensions for Tk 8 and Tcl 8 in a Tcl 9 environmentPARTLY (9.0 branch; main N/A). The original request is fixed: e754018763 + 055d75f68c (trunk, before 9.0.1, 2024-12-21) and fa41fdc007 (core-8-branch); TEA tclconfig c34cded0a3, then 18e57a1c95 (2025-04-08: --with-tcl8 also defines TK_MAJOR_VERSION=8). The rules.vc OPTS=tk8 was later dropped again (effef6c657), and trunk tk.h now has #error for TK_MAJOR_VERSION != 9. However, the 9.0 headers have regressed since Tcl 9.0.4.
-DTCL_MAJOR_VERSION=8 -DTK_MAJOR_VERSION=8 -DUSE_TK_STUBS (what TEA --with-tcl8 passes). Against Tk 9.0 branch tk.h:
tk.h:197: unknown type name 'Tcl_Size'.
#define Tcl_Size int and then #undef Tcl_Size at its end (_TCLSIZEHANDLED), but Tk 9.0 generic/tk.h, tkDecls.h and tkPlatDecls.h use Tcl_Size after #include <tcl.h>.
Status now: Pending (Fixed)
PARTLY (main 9.1b1, 9.0.5, 8.6.18): -relief, -justify and 13 other tag options now reject a bad value and keep the old one. -tabs is still broken in all three versions.
cget (B-work/t026.tcl). -tabs: .t tag configure t -tabs {1c 2c}; catch {.t tag configure t -tabs {1c bogus}} leaves cget -tabs = {1c bogus}. Worse, every later tag configure of that tag, even -foreground blue, then fails with "bad tab alignment" (the foreground is still applied). This is the "-tags" (really -tabs) issue Jan mentioned on 2024-06-04. His branch bug-026e2bb685 (tip e34d9e15a8, 2024-06-04) was never merged and no longer applies to trunk.
tag configure of the tag fails, even for unrelated options (8.6.18, 9.0.5, 9.1). Rebasing bug-026e2bb685 (parse -tabs in a custom option setProc) fixes it; a refreshed version with a test is ready. Not closable until that is merged.
tag cget -tabs = {1c fork} and a later tag configure x -foreground blue fails with "bad tab alignment" / after {1c 2c}, and -foreground works
Status now: Pending (Fixed)
PARTLY (read trunk, core-9-0-branch, core-8-6-branch; the macOS behaviour itself was not tested)
-font case), if ([fp isVisible]) Tk_SendVirtualEvent(fcdPtr->parent, ...) still runs with fcdPtr->parent == NULL when this interpreter never ran tk fontchooser show. Tk_SendVirtualEvent then dereferences the NULL window (Tk_Display(target)).
interp create x; load {} Tk x; x eval {tk fontchooser show}; tk fontchooser configure -font Courier.
show or -parent, but the NSFontPanel is shared and can be visible without that.
tk fontchooser configure -font sends <<TkFontchooserFontChanged>> to a NULL parent whenever the shared font panel is visible without this interp having shown it (e.g. a second interp, or a non-wish host that skipped the exit cleanup). A two-line NULL check (prototype attached) would let this ticket be closed.
Status now: Pending (Fixed)
PARTLY (main, 9.0, 8.6)
msgcat::mc (styles are translated and translated back correctly when the locale is set before first use: {.. 12 bold} round-trips), and the German "Schriftgrad:" label is not truncated (reqwidth == width). Still reproduced in all three versions: if msgcat::mclocale changes after the first tk fontchooser call, the style listbox stays English ("Bold"), while S(style) and Done use the new locale ("Fett"). Picking "Bold" then returns a font without bold. The proposed branch bug-1f46cac080 (2020) was never merged.
msgcat::mc in the namespace eval at source time, while Canonical (called from Show) and Done/Init translate each time. Canonical also appends to S(styles,lcase) in a redundant first loop.
Bold Xbold {}) and passes patched; fontchooser.test 20/20 passes.
bold / after "Xbold" and bold is kept
Status now: Closed (Fixed)
trunk, in main, 9.0, 8.6: Fix 3020550fff: Do not crash or leave dangling entries when grid or place is used on a half-dead windowcore-9-0-branch, in main, 9.0: Fix 3020550fff: Do not crash or leave dangling entries when grid or place is used on a half-dead windowcore-8-6-branch, in main, 9.0, 8.6: Fix 3020550fff: Do not crash or leave dangling entries when grid or place is used on a half-dead windowhalfdead-geometry-crash, in main, 9.0: Do not crash or leave dangling entries when grid or place is used on a half-dead window.PARTLY FIXED. pack and grid were fixed on main by ddfb9848d8 (2024-10-09, fvogel, Fix eb332846f3: GetGrid/GetPacker return NULL for TK_ALREADY_DEAD). 8.6.15 still has the original stale-entry bug for grid/pack (a new window's content is not mapped). REPRODUCED for the rest, see below.
grid .x -in .f in a <Destroy> binding of .f segfaults (main 9.1b1, 9.0.5, 8.6.18; 8.6.15 did not crash). -in sets positionGiven=1 before GetGrid() returns NULL. containerPtr stays NULL, and so does contentPtr->containerPtr, so the code jumps to scheduleLayout and dereferences NULL (tkGrid.c ConfigureContent, containerPtr->abortPtr).
place .f -x 0 -y 0 in .f's <Destroy> binding leaves freed .f linked into its container, causing a use-after-free and a segfault at update / place content (main, 8.6.18). A reuse test gives bad=1 on 8.6.18.
grid .x -in .f crash when run in a <Destroy> binding of .f (8.6.16+ and 9.0). place still has the original problem, which leads to a use-after-free. A prototype fix with tests is ready.
double in 6c1859a0ce (2017-05-19, 8.6.7), which is what the ticket asked for. At script…Status now: Open
Partly FIXED. The internal TkFontAttributes.size became double in 6c1859a0ce (2017-05-19, 8.6.7), which is what the ticket asked for. At script level, sizes are still integers: font create f -size 11.5 fails with "expected integer" (main, 8.6, 8.5), and font actual/configure return rounded integers "for compatibility" (09eec5d40f).
Status now: Open
win-popup-phantom-events, in main, 9.0: Rebase to mainPARTLY (9.1 main): the crossing events are FIXED; the dismissing click still leaks
NEEDS palette mode (not testable: Windows 11 has no 8-bit desktop mode). Both prototypes compile cleanly with MSVC.
NEEDS palette mode (not testable: Windows 11 has no 8-bit desktop mode). Both prototypes compile cleanly with MSVC.
GetDeviceCaps(dc, RASTERCAPS) & RC_PALETTE separately, at the time they are called. So a color allocated in true-color mode and freed after switching to palette mode is not in cmap->refCounts, and Tcl_Panic("Tried to free a color that isn't allocated") fires. The opposite switch leaks palette entries. Repro script: win/1708823fff.tcl (needs a real depth switch while it waits).