tracker issue : CF-4204284

select a category, or use search below
(searches all categories and all time range)
Title:

imagereadbase64() doesn't properly handle transparency

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): CHRIS Z. / ()

Created: 05/02/2019

Components: CFIMAGE

Versions: 2018

Failure Type:

Found In Build/Fixed In Build: 2018.0.03.314033 /

Priority/Frequency: Normal /

Locale/System: / Win 2012 Server x64

Vote Count: 3

Problem Description:
imagereadbase64() function converts transparent pixels to opaque

Same problem as here: https://stackoverflow.com/questions/55201337/saving-jsignature-image-no-longer-transparent

Steps to Reproduce:
https://trycf.com/gist/447c3b9d0aee5ca53bc93449f72f80ae/acf2018?theme=monokai

Actual Result:
colormodel.transparency = "OPAQUE"

Expected Result:
colormodel.transpancy = "TRANSPARENT"

Any Workarounds:

Attachments:

Comments:

This is critical to our production software
Vote by Gareth E.
30692 | May 08, 2019 12:27:53 AM GMT
This bug is duplicate of CF-4204071. The fix will be available with the next HF release (HF11). For patch, please contact on the email shared in the stackoverflow link.
Comment by Nitin K.
30714 | May 13, 2019 08:12:36 AM GMT