CHANGELOG.md

Changelog

v5.8.2

• Modified imports in shrunked.js and ShrunkedImage.jsm. In TB 128 beta the lines like

  ChromeUtils.import("resource:///modules/ExtensionSupport.jsm")
  

  would no longer work properly because they should now be loaded via:

  ChromeUtils.importESModule("resource:///modules/ExtensionSupport.sys.mjs")
  

  (switch from Mozilla-specific JSMs in privileged code to standard ECMAScript modules - jsm -> mjs, you can read about ESM and ESMification here)
  Unfortunately, the new way did not work in the latest stable releases, so I came up with a simple solution to switch between these two ways. There may be a better solution than using try and catch to get the right file to load - I have not seen any solutions to this in the official documentation. Services are now imported automatically, so we have

  const Services = globalThis.Services || ChromeUtils.import("resource://gre/modules/Services.jsm").Services;
  

  which is taken from the TB docs and provides a fallback to the previous import if the TB version used does not yet support global services.

v5.8.1

• Fixed error when autoresize is enabled and resize is set to "on sending mail". When sending email with these settings, autoresize would resize the images and remove them from the list of images to resize. When "when sending email" was selected, the options window tried to be created because there was no check if the autoresize option was turned on and if the options window should be ommitted. Since there was no check if the image list was empty, the code caused an exception that stopped the email sending process. (#26)

v5.8.0

• Added option to also resize images from the original e-mail when using forward / reply (#15). This feature also works with autoresize.\
• Fixed wrong variable name in content_script.js, that caused the log to console option to always be disabled.
• Added a simple "How to use" section to readme.

v5.7.2

• Fixed - the image is not resized when right clicking inline image, selecting resize image and clicking ok. (#23)
  One of the checks (instanceof File) was failing when it should not. I have changed it to .constructor.name, which is more reliable in modern browsers, at least according to a comment on SO.
• Fixed - the context item text is not updated (#23)
  After the context item text was changed when displaying an error (e.g. the image is too small), it was not reset to "Resize this image..." when displayed again for different image.

v5.7.1

• Fixed - Notification not displayed when inserting an inline image (#19)

v5.7

• Added auto resize option for new messages. When enabled, each time an attachment is added / pasted inline, the extension checks if it meets the size restrictions set in the options. If so, the image is automatically resized and saved. (#12)
• Added an option to hide the extra info displayed in the attachments context menu when the file type is not supported (#13)
• Disabled Exif check on PNG files as it sometimes led to PNG files being rejected from resize
• Added 'tabs' to permissions - needed to tidy up the file map and detect the creation of new compose windows
• Added reloading of settings each time a compose window is opened

v5.61

• Fixed wrong version in manifest (#10)
• Fixed some errors being thrown to console (including #11) - added catch to promises and included checking of logging enabled
• Fixed inline image context menu being disabled all the time

v5.6

• Added quality slider to options window (#8)

v5.5a

• Removed strict_max_version from manifest, checked briefly with Thunderbird v115.0 and it seems to be working fine

v5.5

• Added BMP support (inline and as attachment) - bmp files are converted to jpeg when resizing.

v5.4

• Added config option to stop logging messages to console. This required the shrunked.js to have access to webextension's storage.local, which is not available via services or extension context. I've decided to add new api that sets debug to on or off and set the value that way. Probably not the cleanest way to do it, but it works.
• The context menu item is no longer hidden for smaller files (inline images) and unsupported file formats. It is now disabled if the image is too small or of the wrong format and the menu item shows why it cannot be resized. I think this was confusing if someone added, say, a bmp file and tried to resize it, but when opening the context menu there was no resize option available and no additional information.

v5.3

• Added different resampling algorithm - https://github.com/taisel/JS-Image-Resizer In some cases it gives better results than the previous one, usually the images look very similar. However, JS-Image-Resizer supports alpha channel, so it works out-of-the-box for transparent PNGs - this feature was missing in v5.2. Previous algorithm is still available and selectable in options.

v5.2

• Fixed a bug, where the extension settings were ignored and resampling was in fact turned off for all images. This is the main cause of images looking bad after resize. In background.js the settings were loaded into options, and then incorrectly accessed. Changing in background.js from

    exif: options.exif,
  

  to

    exif: options['options.exif'],
  

  i.e. accessing each option through full key e.g. "options.exif" fixed the problem. I am not sure if the way of accessing the storage has changed recently or if this was wrong from the beginning

• Added PNG to Exif header detection. Due to options reading bug the Exif module was not used previously and I did not see the "Not a JPEG" exception when adding PNG files. Apart from checking the correct magic bytes nothing more was added to Exif module, so probably copying PNG Exif data will not work.

• Fixed a bug, where the "Automatically rotate images" option could not be selected. This was cause by using options.orient instead of options.orientation in one place of config.js.

• Changed extension id, added readme and changelog

Added in previous commits

• PNG Support
• PL lang support