ThunderBlog

I modified the bug reporter I use to now email users on updates to their bug/issues they file. So when I update the bug from my backend, you will get an email notifying you that an update has occurred.

It’s now available on AMO.

I’ve ran the checks, and everything went just fine. I have uploaded the version to AMO a few minutes ago.

I just have to run the final checks (update the what’s new page) and then it can be uploaded.

It’s still being translated. Still. Though it has sped up a bit in the last few days.

I am aware of several bugs in ThunderBrowse that are new in 3.2.1.8, these are fixed in 3.2.1.3:

• https redirects: This was fixed once I encountered it. Somehow, the https fell off the registered protocols list (probably when I was working on something else).
• The LiveJournal and/or other POST form failings: This involves encoding user inputs for POST requests. This is removed for POST requests only. GET still encodes.
• A form input type of button will never do anything: Now it submits the document. If it has an onclick element, it may or may not fire it. If it does, a copy of the site may open in firefox, and still load just fine in Thunderbird. It’s kinda like how onsubmit worked.
• Clicking on a link in a cached tab page will cause it to open in firefox: This seems to be unfixable at the extension level, and involves the Thunderbird core. There is a workaround and can be found in the notes section in this bug report.

For the first and second bug, both of them have public patches available on the bug database.

Thank you all for being patient.