July 2021 Release Notes (Nissenbaum Release)

  • Updated

All Osano releases are now named after famous contributors in the world of privacy in all shapes and forms! For this release, our team selected Helen Nissenbaum for her contributions to privacy rights. Learn more about Helen Nissenbaum and why we chose her. 

Here's what's new for this Nissenbaum update in July 2021:

NOTE: This release contains changes to the consent manager code base. If possible, please be sure to test any changes in a pre-production environment prior to publishing into production.


  • Customize Cookie Popup Text [Enterprise Only]
    • Enterprise Users can now customize certain text fields within the Osano cookie popup. These customizations include the following: 
  • Data Discovery (Preview) - Osano's new Data Discovery features will allow you to understand what customer data you have and where it is located.
  • Consent Manager API [Copy Configurations] - Osano now provides an API for copying Osano Consent Manager configurations via API. Read more about the Copy Configuration API (login required). 
  • Vendor Monitoring: Upload Vendor Documents [Enterprise Only] - users can now upload documents to Product and Vendors.
    • Supported files include: .ppt, .pptx, .odp, .key, .doc, .docx, .pdf, .odt, .rtf, .txt, .xls, .xlsx, .ods, .xlsm, .csv, .jpg, .jpeg, .png, .svg

Enhancements (June-July 2021)

  • CMP UI Enhancement - Renaming of the "Styling" tab in Consent Management to "Customizations."
  • CMP API Enhancements - New Calls and Enhancement to current calls. See Developer Documentation for additional details. 
  • Language Translation Updates. 
    • German 
    • Romanian
    • Italian
    • Russian
    • Chinese Hong Kong (zh-hk) 
    • Chinese Taiwan (zh-tw)
    • Arabic, Hebrew, Persian/Farsi: Right to Left Language Support Updates - UI change for all supported RTL languages. On/Off Toggles made consistent with RTL formatting.
  • Added "Etag" header support.
  • Improved logic around iFrames blocking. This logic has been implemented to address an issue when setting iFrame mode to Permissive, Strict, or Debug.
  • Support for "smooth scroll" for Chromium browsers. CSS enhancements added to CMP to support the smooth scroll functionality in Chromium browsers which is affected by an existing Chromium bug
  • Cookie Length Enhancement: Addressed a situation where Cookie keys could cause the string length to surpass the cookie limit, which causes certain cookies not to be set. 
  • Added path lookup matching for quick classification of iframes and script-src dependency updates. 
  • Added an enhancement that allows requestAnimationFrame to run in hidden windows on Chromium browsers. 

Bug Fixes (June-July 2021)

  • Consent Manager (CMP)
    • Fixed a bug in the Osano CMP API where the 'osano-cm-consent-saved' event was triggering on all subsequent page loads after 'save' event.   
    • Fixed an issue where the Osano CMP could potentially modify the "Type" property of specific tags. 
    • IAB TCF 2.0 Purpose Consent Enhancement: new logic for vendor purpose consent and updated vendor-list file to IAB framework testing.
    • IE11 EventTarget fix for legacy browser support: IE 11 no longer supports EventTarget. A fix has been put in place to utilize Node.prototype when EventTarget.prototype does not exist.
    • Google Pay + Google Pay Store Bug, which interfered with Google Pay capabilities in some situations. This has been addressed.  
    • Maximum Stack Size Exceeded Console Error Fix - Fixed an issue where setting script-src could negatively impact performance in certain scenarios. 
  • B2B Web App (my.osano.com)
    • Fixed an issue where UI fields within the B2B web application (my.osano.com) would occasionally erase or undo previous UI updates. This issue was most evident when making updates to a consent configurations classification UI.
    • Fixed an issue in the B2B web application (my.osano.com) where a user could not update a consent configuration in the web app UI unless they refreshed the page.
    • Fixed an issue where adding custom optional email fields to a DSAR form would block the form from being submitted.