v10.36 2026-07-25 WeKan ® release

This release fixes the following bugs:

• The Change profile image window (Member settings > Change Avatar, and the same window in Admin Panel > People) rendered each avatar row’s “Delete” link and file name INSIDE the row’s select link. An <a> inside an <a> is invalid HTML: the browser closes the outer anchor, so the file name and the Delete link fell out of the row’s flex layout and rendered as bold text floating at the right edge, and a click on Delete also selected that avatar. Delete and the file name were shown only for the avatar currently in use, so no other upload could ever be deleted, and an empty p.sub-name added a stray block in the middle of the row. Each row is now one flex line - thumbnail, file name (truncated with the full name as a tooltip), a check mark when it is the avatar in use, and a delete button that is a SIBLING of the select link, so deleting never also selects and every uploaded avatar can be deleted. The row in use is highlighted like in the other pop-over lists, the initials row shows its “Default avatar” label under the name, and the upload hints (max filesize, allowed filetypes, invalid filename) are grouped into one muted paragraph above the upload button. Deleting the avatar in use left profile.avatarUrl pointing at a file that no longer existed - a broken image everywhere - so both windows now fall back to the initials when the deleted file is the one in use. The Admin Panel window also passed userData= to userAvatarInitials, which reads this.userId, so its initials rendered empty. Thanks to xet7.
• On iPad Safari a full-screen “Uncaught runtime errors: ERROR Script error.” panel appeared after login, and again when the Safari Share sheet was opened on All Boards to add WeKan to the home screen. That panel is webpack-dev-server’s error overlay, shipped by the rspack DEV server only - a production build has no dev server and no overlay. It opens for every window error event, including ones that carry no information: a browser sanitises an error thrown by a CROSS-ORIGIN script to the bare message “Script error.” with no error object and no stack, and iOS Safari raises those from its own machinery and from content blockers and extensions, which is what the Share sheet triggered. It cannot come from WeKan’s own code, because the bundle is served same-origin (no CDN_URL), so a real WeKan error always reaches the overlay with its actual message and stack. The overlay now ignores exactly that one message and still shows every other runtime error and all compile errors. Thanks to xet7.
• The board bar (the second header bar) fits on one line on iPad. In landscape it wrapped onto two rows - board title, edit, visibility, watch, star and sort on the first, Filter / Search / view / dependencies / multi-selection / hamburger on the second. Measured at a 1180 CSS px viewport the two rows needed about 1304px on one line, ~124px more than the viewport, and nearly all of that is per-button empty space rather than text: each button carries 12px side margins, 10px on each side of its icon and a 10px gap after its label, about 54px of chrome around a ~60px icon+label. So nothing has to be hidden at that width: halving the chrome between 801px and 1400px frees ~295px, which fits the bar on one line with room to spare for languages with longer labels, and icon and label sizes are untouched so the buttons stay comfortable to tap. In tablet portrait (820px), where even the halved chrome cannot fit the labels, they drop to icons only between 801px and 1000px - the same treatment phones already get below 801px, with titles, tooltips and popups unchanged. Wide desktops, which never wrapped, look exactly as before, and phones keep their 44px touch targets. Thanks to xet7.
• A long board title now moves ALL of the board bar’s buttons to its second row, under the title. Before, the controls were split across the two rows: the title kept the left group (edit, visibility, watch, star, sort) beside it and only the right group (Filter, Search, view, dependencies, multi-selection, hamburger) wrapped underneath. That is what separate flex items do - the title and the three button groups were four children of the header row, so the row broke wherever it ran out of width. The three groups now live inside one wrapper, so the row has just two items, the title and the buttons, and either the buttons fit beside the title or the whole set moves down together. A short title is unaffected, because the wrapper measures as its own content width and only moves down when it genuinely does not fit. A title longer than the whole bar now wraps inside the title instead of overflowing the viewport. Thanks to xet7.

Thanks to above GitHub users for their contributions and translators for their translations.