Thunderbird 128 doesn't allow URLs for Icons #1
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: mmk2410/SpaceApper#1
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Starting with Thunderbird 128 it is no longer possible to specify any random URL for the icons of the Space entries. As far as I understand, only so-called "strictRelativeUrl"s are allowed. I tried passing an object URL to a blob instead but that is also refused. Since it also doesn't seem that an extension can store or access files locally (tbh I rather glad about that in general. Though, an isolated folder on the file system wouldn't hurt) I cannot download and store icons at runtime and create the Spaces entries using these.
The current result is, that the application crashes at startup and does not create any spaces at all. I could disable the custom icons but this means (at least at the moment) that the extension icon is used for all entries which makes them a bit hard to distinguish (read: no possible at all).
As far as I can see there is no option at all for fixing this and showing the web app icons in the Spaces toolbar.
I have one possible workaround in mind: create numerous icons with just to letters (e.g. Yo or Lo) and use them automatically based on the first to letters of the web app name. While this could lead to collisions it would at least be some possibility to continue this extension.
But to be frank: Given this setback as well as the other currently ongoing problem that the listeners for changing the User-Agent on the web app pages is only working for about 30 seconds after Thunderbird is started because then the background script is killed really strain my motivation to continue working on this... We'll see.
This issue is crossposted to my Forgejo instance as well as GitLab and GitHub.