Releases: eyalroz/bidimailui
Version 0.15.2: Thunderbird 128 compatibility, bug fixes
Changes relative to 0.14.1:
- Compatibility: Compatible with Thunderbird 128.* - mostly.
- Compatibility: Not compatible with Thunderbird 115 and earlier
Unresolved TB 128 compatibility issues
Note: The extension is fully compatible with TB 115 except for this issue:
- #102 TB developers broke the main toolbar, and the new "unified toolbar" is difficult to get buttons onto. How to do so is not documented, and I have not figured it out yet. Toolbars on individual message reading and message composition windows work fine.
Significant bug fixes:
- #125 Restored some of the corrective recoding capabilities, which had regressed due to failure to pass some relevant parameters to the function performing the recoding. Note this cannot get us back to the TB 91 quality of mis-decoding correction, as it is still impossible to force a different character set for the basic decoding.
Resolved TB 128 compatibility issues
- #123 Now importing JSM modules using new mechanism (
importESModule
) - #124 Now using ChromeUtils instead of XPCOMUtils for the
defineLazyGetter()
method
Cosmetic & minor issues:
- #118 Fixed typo in link from the extension's info page to this website
- #122 Thunderbird busted the pop-up option selection textbox, so we've shortened the option text to fit the now-shortened list box
- #126 Making sure to setting attributes to strings, not other values
- #127 Avoid warnings about document direction being adopted from the body direction - by making sure directions get set on the document element rather than the body.
Version 0.14.1 - Regression fixes
- Compatibility: Compatible with Thunderbird 115.* - almost (see this version).
- Compatibility: Not compatible with anything else :-(
Bug fixes:
- #99 Stop messing up the message subject label by corrective recoding
- #112 Avoid throwing an exception when the 3-pane window has no message displayed
- #113 Skipping useless corrective recoding of the weird header-in-body tables (don't worry, you don't see them as a user anyway)
- #114 No longer trashing the console with debug messages about chrome injection/overlaying
TB 115 compatibility + partial restoration of charset misdetection capabilities
- Compatibility: Compatible with Thunderbird 115.* - mostly.
- Compatibility: Not compatible with Thunderbird 102 and earlier
Unresolved TB 115 compatibility issues
Note: The extension is fully compatible with TB 115 except for this issue:
- #102 TB developers broke the main toolbar, and the new "unified toolbar" is difficult to get buttons onto. How to do so is not documented, and I have not figured it out yet. Toolbars on individual message reading and message composition windows work fine.
Other bug fixes:
- #30 Correctly detecting direction on reply in more cases
- #98, #97 (Among other things, ) now properly performing corrective recoding when we're able to - even if we've not been allowed to trigger a character set change and a reloading of the message.
- #103 The Ctrl+Shift+X key, which was often/mostly broken in v0.13 of the extension with TB 102, now workers properly with TB 115
- #76 Removed a debugging-related menu item which had snuck into the last release by mistake
- #110 Respecting the initial direction preference with v115
Cosmetic & minor issues:
Version 0.13: TB 102 compatibility
Version 0.12 - Thunderbird 91 compatibility
-
Compatibility: Compatible with Thunderbird 78., 91.1 and likely all 91. versions.
-
Compatibility: Not compatible with Seamonkey 1.x, Toolkitized Seamonkey (2.x).
-
Compatibility: May be compatible with Thunderbird 68.* .
-
Now separating the user's preferred display charset in Thunderbird from the user's preferred single-byte charset for the mis-decoding correction of BiDi Mail UI.
Internal changes (no user visibility):
- Now using preference
"extensions.bidiui.mail.display.preferred_single_byte_charset"
. - Removed some not-really-package-specific utility code in favor of standard Javascript facilities and the
Preferences.jsm
module - No more need for the paragraph splitting/merging code, Thunderbird does this for us these days.
- Updated the extension loader ("WindowListener") version to 1.56
- Reworked the extension's build script
- Removed the
bidimailui-preftree.xul
file, an unused remnant of Seamonkey support.
Version 0.12.0 beta 1
A preliminary release which should support Thunderbird 91.
Version 0.11 Release Candidate 1
- Compatibility: Compatible with Thunderbird 68, 78 and probably all beta versions in-between.
- Compatibility: No longer compatible with Seamonkey 1.x, Toolkitized Seamonkey (2.x)
- Compatibility: No longer compatible with Thunderbird 30...67.
- Fix: Was using an identifier instead of a string, messing up some of HTML message composition support
- Fix: Was missing an XHTML sub-namespace for the preferences/
- Fix: Issues mostly (wholly) resolved the issues with setting the direction in new messages.
- Fix: Now properly accounting again for the message subject in direction detection, and setting its direction again.
Internal changes (no user visibility):
- No longer using JARs within the XPI
- Reworked the directory structure
- Dropped some files only in use by previous TB versions (but not all files for now)
- Using John Bieling's privileged extension loader, from here; see this guide regarding how to use it.
- Now using service getters provided by
Services.jsm
andMailServices.jsm
whenever possible. - Now logging using a plain and simple
console.log()
. - Fix: Was adding stylesheets to documents as children of the root element rather than the head element.
- Fix: Now creating non-XUL for style elements for appending rules without a link.
- Fix: Passing correct parameters to reply-body direction detection.
- Fix: No longer using editor.setParagraphFormat().
- Fix: No longer using the now-gone interface nsIEditorStyleSheets to append stylesheets.
Version 0.10.1.1
- Fix: Was using an identifier instead of a string, messing up some of HTML message composition support
- Fix: Was missing an XHTML sub-namespace for the preferences/
- Extension homepage link now points to the GitHub repository.
This is probably the last version to support Seamonkey 1.x, Seamonkey 2.x (suiterunner) and Thunderbird versions below 68.
Version 0.11 beta 3
- Compatibility: Compatible with Thunderbird 68, 78 and probably all beta versions in-between.
- Compatibility: No longer compatible with Seamonkey 1.x, Toolkitized Seamonkey (2.x)
- Compatibility: No longer compatible with Thunderbird 30...67.
- Fix: Was using an identifier instead of a string, messing up some of HTML message composition support
- Fix: Was missing an XHTML sub-namespace for the preferences/
- Fix: Issues mostly (wholly) resolved the issues with setting the direction on new paragraphs.
Internal changes (no user visibility):
- No longer using JARs within the XPI
- Reworked the directory structure
- Dropped some files only in use by previous TB versions (but not all files for now)
- Using John Bieling's "WindowListener" from here, as an extension loader; see this guide regarding how to use it.
- Now using service getters provided by
Services.jsm
andMailServices.jsm
whenever possible. - Now logging using a plain and simple
console.log()
. - Fix: Was adding stylesheets to documents as children of the root element rather than the head element.
- Fix: Now creating non-XUL for style elements for appending rules without a link.
- Fix: Passing correct parameters to reply-body direction detection.
- Fix: No longer using editor.setParagraphFormat().
- Fix: No longer using the now-gone interface nsIEditorStyleSheets to append stylesheets.
v0.10
- Compatibility: Thunderbird version upto 68.*, inclusive. This actually involved quite a lot of changes under the hood.
- Compatibility: Seamonkey compatibility should have improved, but this has not been effectively tested.
- Fix: Seamonkey preferences dialog was trying to load a no-longer-existent function.
- Preferences for the extension are now named
extensions.bidiui.mail.some_pref_name
rather thanbidiui.mail.some_pref_name
- Now avoiding the Error Console message about an error with a
contentaccessible=yes
line in chrome.manifest