Quicktext v6 has reached its third milestone in being converted to the WebExtension technology. The ultimate goals of this effort are described in the migration overview. Everything mentioned there is still important, so if you have not read that, please do so soon.
The old XUL-based settings dialog has been fully replaced with a pure WebExtension settings manager. File system access (file picker, file read/write) is still provided by a FileSystemAccess Experiment API, which continues to rely on XPCOM — that last legacy dependency will be addressed in Milestone 4.
What changed
New HTML/CSS/JS manager
The manager is a standard WebExtension dialog using HTML, CSS, and vanilla JavaScript with ES modules. It preserves the same four-tab layout (General, Templates, Scripts, Advanced) and should be fully on par with the old XUL dialog in terms of features.
Toolbar was moved into the Quicktext Legacy Companion Add-on
The Quicktext compose toolbar that was part of the old Quicktext XUL interface cannot be reproduced using WebExtension APIs. It has been moved into a separate Quicktext Legacy Companion Add-on, which uses a custom Experiment API to inject the toolbar. Users who rely on the toolbar need to install the companion add-on alongside Quicktext. The companion add-on will only ever be made available for Thunderbird ESR, while the future Quicktext version will run on Thunderbird Release without requiring regular updates.
Nested flyout variables menu
The original XUL dialog used native nested menus, which are not available to WebExtension pages. To stay as close to the original behavior as possible, an HTML/CSS flyout menu was implemented using @floating-ui/dom.
Direct file system access still depends on an Experiment API
Quicktext still supports reading files directly from the file system, but most parts have been marked as deprecated and will be removed by the work planned for Milestone 4.
Direct file system access to include static files will be replaced by a virtual file system. Users relying on includes of non-static local files are encouraged to explore migrating to a URL-based include now, either from a real remote system or from a local web server exposing parts of the local file system. Python's built-in HTTP server is a simple option:
python3 -m http.server 8080 --directory /path/to/files
ATTACHMENT and IMAGE: FILE and URL modes
The variables menu now exposes both FILE and URL modes for the ATTACHMENT and IMAGE tags, matching what the parser already supported but the old menu never surfaced. The deprecated FILE mode opens a file picker; the URL mode inserts a placeholder the user can edit directly in the template body.
Locale hygiene
As part of this milestone, all locales were normalized and cleaned.
Quicktext v6 has reached its third milestone in being converted to the WebExtension technology. The ultimate goals of this effort are described in the migration overview. Everything mentioned there is still important, so if you have not read that, please do so soon.
The old XUL-based settings dialog has been fully replaced with a pure WebExtension settings manager. File system access (file picker, file read/write) is still provided by a
FileSystemAccessExperiment API, which continues to rely on XPCOM — that last legacy dependency will be addressed in Milestone 4.What changed
New HTML/CSS/JS manager
The manager is a standard WebExtension dialog using HTML, CSS, and vanilla JavaScript with ES modules. It preserves the same four-tab layout (General, Templates, Scripts, Advanced) and should be fully on par with the old XUL dialog in terms of features.
Toolbar was moved into the Quicktext Legacy Companion Add-on
The Quicktext compose toolbar that was part of the old Quicktext XUL interface cannot be reproduced using WebExtension APIs. It has been moved into a separate Quicktext Legacy Companion Add-on, which uses a custom Experiment API to inject the toolbar. Users who rely on the toolbar need to install the companion add-on alongside Quicktext. The companion add-on will only ever be made available for Thunderbird ESR, while the future Quicktext version will run on Thunderbird Release without requiring regular updates.
Nested flyout variables menu
The original XUL dialog used native nested menus, which are not available to WebExtension pages. To stay as close to the original behavior as possible, an HTML/CSS flyout menu was implemented using @floating-ui/dom.
Direct file system access still depends on an Experiment API
Quicktext still supports reading files directly from the file system, but most parts have been marked as deprecated and will be removed by the work planned for Milestone 4.
Direct file system access to include static files will be replaced by a virtual file system. Users relying on includes of non-static local files are encouraged to explore migrating to a URL-based include now, either from a real remote system or from a local web server exposing parts of the local file system. Python's built-in HTTP server is a simple option:
ATTACHMENT and IMAGE: FILE and URL modes
The variables menu now exposes both
FILEandURLmodes for theATTACHMENTandIMAGEtags, matching what the parser already supported but the old menu never surfaced. The deprecatedFILEmode opens a file picker; theURLmode inserts a placeholder the user can edit directly in the template body.Locale hygiene
As part of this milestone, all locales were normalized and cleaned.