image-thumb | NodeJS image thumbnail server | Computer Vision library

Currently you're injecting code in page context which is both an unnecessary overcomplication and wrong as you inject the background script which already runs in the hidden separate background page of the extension that's not related to the web page. See how to open background.js devtools and console.

Remove script_injection.js, injection_ui.js and web_accessible_resources section and unnecessary permissions from manifest.json as well as jquery.js.

Declare parameters of onMessage listener correctly per the documentation.

Use "persistent": false, more info.

Short answer: If you discard the ICC color profile from the JPEG, there's no way to ensure the colors will be correct (unless you also fully control the reading of these files).

However, the current code does not just "discard" ICC profiles, instead the images will always end up as plain RGB color space, using sRGB profile, and will be properly converted by Java2D along the way. As the sRGB profile will typically not be embedded, your images will display as intended using software that uses sRGB as default profile.

Long answer:

1. Passing true for the ignoreMetadata of ImageReader.setInput method, is simply a hint to the reader that it may ignore meta data. It does not enforce skipping meta data (and most likely, an ICC profile should not be considered metadata anyway). From the JavaDoc:

   The ignoreMetadata parameter, if set to true, allows the reader to disregard any metadata encountered during the read. [...] The reader may choose to disregard this setting and return metadata normally.

2. When dealing with BufferedImages in Java, images will always use a color profile. Your oldImage should either have its original color profile from the JPEG, or be converted from this profile to sRGB. Exactly how this works (if at all) is entirely plugin dependent. But to the best of my understanding, the standard ImageIO JPEG plugin will read the embedded ICC profile, and convert the results to sRGB.

3. Exactly what happens when you use Image.getScaledImage I'm not sure, as the old AWT Image API is not something I use. Most likely, the image was already using sRGB and will still use sRGB profile. It should not modify color.

4. In any case, newImage will always be RGB in sRGB profile, as there is no profile information carried over to the BufferedImage constructor used. Non-RGB images will always be TYPE_CUSTOM, and thus converted to TYPE_INT_(A)RGB. Note that images with alpha channels will typically not be interpreted as intended by other JPEG software, and I believe support was removed from recent JDKs, so my advice is to always remove any alpha channel before writing as JPEG.

5. Finally, writer.write (without any metadata) will, for the standard ImageIO JPEG plugin simply write the image as JPEG in JFIF format (if possible). It will only write an ICC profile if the image to be written is in a non-standard profile. For sRGB it will not write one (I'm assuming imageWriteParam are all defaults).

PS: The original JFIF format did not specify a default color profile, but I believe later amendments (like IEC 61966-2-1) does specify sRGB as default. The Exif format allows specifying sRGB as the color profile without actually embedding it, by setting the Exif ColorSpace tag (tag 40961) to 1. The standard JPEG plugin does not write Exif files (without significant code on your part).

You can verify most of the statements above by carefully studying the source code for the JDK.

You can fix this one by just setting 100% width on .editor.

Since the parent already has flex-wrap: wrap, this should work out just fine for you. The content below the editor will just wrap to below it.

It is possible to clean this tag using regex. In this example, I will use two conditions to clean this HTML up.

I could not construct a div out of Base64 images, otherwise I could mangage to acheive that through CSS.

Wrap a div around the image

For anyone who's struggling with this, it looks like swiper has a bad time with dynamic slides with looping. Setting loop: false seems to work

Yes might be links are outdated, refer swiperjs for latest version and try this links:

I would not add two separate collections, I would use just one and send back via API only the needed data. You can use GraphQL if you want to segment super specifically the data you send back.

But in terms of Mongo architecture I have never heard of separating collections.