• change camel-case hint text for chinese translations

Update highlightjs version to 11.11.1

• Fix markdown parser to respect parseAsInline option #8917.
• Fix improper parsing of macrocall, whenenver args contain > character.
• Use $tw.log.MARKDOWN flag to enable debug messages.

Remove deprecated plugins and editions and some legacy plugins, including:

• Blog
• Cecily
• D3 Plugin and its demo
• HammerJS
• Highlight (Legacy)
• Markdown (Legacy)
• Mobile Drag And Drop Shim Plugin
• nw.js Saver
• TahoeLAFS and its demo

This note addresses two major bugs introduced in the Freelinks plugin with the v5.4.0 release:

Fixes: * First Character Loss: The first character of a matched word would incorrectly disappear (e.g., "The" became "he"). This was fixed by correctly timing the filtering of the current tiddler's title during match validation, ensuring proper substring handling. * False Positive Matches: Unrelated words (like "it is" or "Choose") would incorrectly link to a tiddler title. This was resolved by fixing wrong output merging in the Aho-Corasick failure-link handling, eliminating spurious matches from intermediate nodes, and adding cycle detection.

Impact: * Significantly improved correctness and reliability of automatic linking for all users, especially in multilingual and large wikis.

Fixed issue where the browser storage plugin caused the wiki to be marked as dirty every time it starts up. The problem was due to the use of a log tiddler titled $:/info/browser/storage/persisted, the fix is to rename it to $:/state/browser/storage/persisted.

• If macro list-links-draggable misses the tiddler parameter it points to currentTiddler variable by default now
• Also discussed at Talk Tiddlywiki

Adds tablist, tabpanel and tab roles to the tabs macro to improve its accessibility. It also adds a selectedAria attribute to the button widget.

Make some core classes display properly when Tiddlywiki's language uses bidrectional scripts.

Replaces hardcoded fill attributes with one fill: currentColor rule to solve the compatibility issues of migrating to lucide icons.

This PR introduces a new filter run prefix :let that assigns the result of the filter run to a variable that is made available for the remaining filter runs of the filter expression. It solves the problem that previously it was impossible to compute values for filter operator parameters; parameters could only be a literal string, text reference or variable reference.

This PR also introduces multi-valued variables, the ability to store a list of results in a variable, not just a single string. They can be assigned with the new :let filter run prefix, or the existing <$let> widget. The full list of values can be retrieved using round brackets instead of the usual angle brackets. In all other contexts only the first item in the list is used as the variable value.

• Multi-Valued Variables
• Let Filter Run Prefix
• LetWidget

The import UI now displays import options based on the file types being imported. Import options are only shown when relevant files are detected, an example is:

tags: $:/tags/ImportOptions
condition: [match[text/x-markdown]] :or[match[text/markdown]]

The attribute clamp is added to the RevealWidget to force the popup to be displayed inside its container without overflowing. The value can be right, bottom or both. Clamping to left and top can be accomplished via the positionAllowNegative attribute.

Allow LinkWidget to use all aria attributes directly.

Fixed a bug in the RevealWidget, DroppableWidget, EventcatcherWidget, and KeyboardWidget where an empty class attribute would generate a leading space in the rendered HTML. By trimming the resulting class string, we shorten the HTML and avoid potential confusion.

Edit-text widget rows parameter takes precedence

PR #8972 introduced a change in the ActionLogWidget that could lead to a significant slowdown, which has been fixed.

The following math operators are changed to output an empty list when the input list is empty:

• sum[]
• product[]
• maxall[]
• minall[]
• average[]
• variance[]
• standard-deviation[]

Added the jsondelete operator for deleting properties from JSON strings. The operator uses the same code path as jsonset to locate the correct part of the object, ensuring consistency between setting and deleting operations. It supports deleting both object properties and array elements, with support for negative array indexes counted from the end.

Add a new parameter for sort, nsort, sortan, sortcs and nsortcs to support sorting with a custom locale.

decodebase64 Operator now outputs error to the filter operator result.

The web server's get-file route now supports HTTP Range requests and file streaming, enabling better loading and playback of large media files.

Features

• HTTP Range header: Enables partial content delivery with 206 Partial Content responses, which is used when the user drags the progress bar in video/audio playback
• Streaming file delivery: Browsers can now properly seek and stream video files from the /files/ directory. Files are read using Node.js streams for better performance and memory efficiency.
• Resumable downloads: To save interrupted downloads

This PR adds the **/output/** directory to eslint ignore configuration

• skip reading file content when _canonical_uri is present
• skip loading file when file size is too large

This PR changes the default AES encryption setting from 128 bit to 256 bit.

• Download emtpy.html v5.3.8 from the archve which uses AES 128 bit
• Create some content
• Save encrypted as eg: aes-128.html
• Create aes-256.html with TW v5.4.x
• Create some content
• Save encrypted as: aes-256.html

Import decryption test

• Import aes-256.html into aes-128.html -> Decryption and import works
• Import aes-128.html into aes-256.html -> Decryption and import works

This change reduces the size of the core plugin by 119.3KB or about 4.5%.

Removes nested <span class="tc-keyboard"> element in core search field.

Replace base64-utf8 module with TextEncoder method to convert between utf-8 and Base64.

Doing so enables us to filter and group changes. For example, we could show all the breaking changes between two releases.

Tiddlers were previously processed before shadows during module registration. The shadow modules registration algorithm only checked for a matching title to prevent overwriting, but a differently named tiddler with the same exports would be overwritten by a shadow. This change swaps the order of $tw.wiki.defineTiddlerModules() and $tw.wiki.defineShadowModules() in boot.js, so that tiddlers are processed after shadows and can therefore override them.

Each group (tiddlers or shadows) is sorted alphabetically, so plugin shadows would previously correctly overwrite core shadows (assuming their name starts with $:/plugins/), which remains unchanged. This change only affects module tiddlers that have the same export as a shadow, but a different name.

Remove redundant code in core/modules/filters/format/json.js.

Remove Opera & Microsoft prefix in $:/core/modules/utils/dom/browser.js.

Fix the problem that tiddlywiki's raw markup shadow tiddlers in $:/core is not included in HTML.

CSV parser used to support only the very obscure text/tab-delimited-values mimetype so this change adds the more common text/tab-separated-values.

Refactor base64 utility functions in $:/core/modules/utils/utils.js to make it easier for maintainence.

• Split base64 utility functions to two platforms
• Use TextEncoder and TextDecoder api in Node.js
• Do not export base64ToBytes and bytesToBase64

Functions returning cached tiddler lists now return shallow copies to prevent external code from inadvertently mutating the cache

This PR introduces a new utility $tw.utils.serializeWikitextParseTree() that can convert WikiText Abstract Syntax Tree (AST) nodes back into wikitext strings.

There is also a utility serializeAttribute for a single attribute node, like an attribute of a widget.

Use Cases

• Programmatically manipulating wikitext content by modifying the AST, and use this to write it back
• Building WYSIWYG editors
• Creating wikitext formatters and linters

Implementation

• New core plugin tiddlywiki/wikitext-serialize containing most of the logic
• Separate serialize handlers for each WikiText rule as module-type: wikiruleserializer
• Test suite with tag $:/tags/wikitext-serialize-test-spec
• It uses each parser's name as rule (nextMatch.rule.name), each AST node that needs serialization has a type property matching the rule name
  • HTML tags and widgets are handled by the html serializer

Example Usage

// Parse a tiddler's wikitext to AST
var parseTree = $tw.wiki.parseTiddler("MyTiddler").tree;

// Serialize AST back to wikitext string
var wikitextString = $tw.utils.serializeWikitextParseTree(parseTree).trimEnd();

This feature offers new tools for JS plugin developers. It is not a user-facing change.

This adds support for async functions to commands and startups.

In both synchronous: true and synchronous: false mode, if you return a promise (manually or by using the async keyword), it will wait for the promise to resolve, and then proceed using the resolved value as the return value of the function.

Importantly, in synchronous: false mode, returning a promise will not change the callback behavior. So you can safely use an async function and still call the callback to continue execution.

Previously, in synchronous: true mode, returning a promise would have just logged the promise to console and halted execution. Now the promise will be awaited, and if the value is truthy, it will be logged to console and halt execution. If the promise resolves to a falsy value, execution will continue. This is the main breaking change, but since logging an opaque promise to console is the most useless of all error messages, this is unlikely to seriously break anything in practice. Throwing anything, truthy or not, will still stop execution (in synchronous: true mode).

This also does not add any error handling code. Rejected promises should still be logged to console as unhandled rejections just as uncaught exceptions are currently.

Updates the eslint config to check for syntax newer than ES2017. This uses a plugin to check for newer syntax, for better error messages, and may need to be updated regularly along with eslint to catch the latest features.

Mark CSS macros supported in 2017 baseline as deprecated. They are moved to $:/core/macros/deprecated now.

Deprecate some utility functions. Some of them are moved to $:/core/modules/utils/deprecated.js.

This PR adds:

• th-dom-rendering-element hook, that is called right before the DOM node is inserted into the DOM
• It allows plugins to add debug info
• An example using an experimental hook can be found at: #9222

Modules in draft tiddlers should not be executed.

This PR:

• Checks for drafts in $tw.Wiki.prototype.defineTiddlerModules
• It also reports and blocks draft modules that come from plugins

Migrate eslint deprecated rules (except for nodejs related rules). Format related rules are replaced by @stylistic/eslint-plugin.

This PR modifies $tw.utils.repackPlugin() so that it adds the standard tiddler modification fields to plugin tiddlers when they are repacked.

• Enforce tab indentation, semicolon
• Switch off max-classes-per-file
• Switch on no-eval rule and disable it in $:/boot/boot.js with one comment
• Show warning for unused variables
• Disable @stylistic/indent rule in $:/boot/boot.js and $:/boot/bootprefix.js

Migrate the unmaintained diff-match-patch library to the maintained and modern fork diff-match-patch-es.