-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with column widths on TB startup #24
Comments
There is old issue #7, which is most likely unrelated (pre-Supernova TB) and a comment in #14 (from 2024-05-17). So far I have witnessed this behavior only once and I don't know a reliable way to reproduce it. The columns reverted back to normal when switching folders, so I didn't got a chance to debug it. There were no significant messages in TB console. Until it appears again on my PC or I find a way to somehow reproduce it, there is not much I can do about it. |
Upon further investigation, it looks like some kind of race condition between adding custom columns and restoring saved/default folder settings. I'll try asking TB team to confirm whether this is a bug in the client. |
Temporary workaround: switch to some other folder you don't really care about and select "Restore default columns". This will reset settings for that folder, but as a side effect it will update |
Looks like a bug in TB: https://bugzilla.mozilla.org/show_bug.cgi?id=1909621 |
Sounds plausible; I also had the impression, that this may be a timing problem, kind of. As workaround I switch off/on the AddOn, so any columns' settings will not be affected. |
Should be fixed in Thunderbird 134. |
Since rev. 1.1.2, there is still a problem with the emails' list (a similar issue was already mentioned by another user some weeks ago):
In most cases, after starting TB
After deactivating/reactivating the AddOn (without restarting TB) the list is ok.
Applies to: TB 115.12.2, AddOn Rev. 1.2.0
Screenshot (top half shows the correct list, bottom half shows the problem):
The text was updated successfully, but these errors were encountered: