Tealeaf Web SDK release notes
Released on January 13, 2026
Bug fixes
- Fixed a console error thrown by Ajax Listener when certain API responses were empty.
- Fixed an Ajax Listener error when the first parameter of fetch was a URL resource object.
Improvements
- Ajax Listener option to enable cooperative chaining so the module can better coexist with other tools
- Ajax Listener option to fall back to using the performance
- Observer API when other tools block its use of Fetch and XHR
- Ajax Listener URL filter now matches on full HREF rather than pathname only.
- Ajax Listener new debug logging option
- Ajax Listener now captures API query string parameters.
Tip
To learn more about these options, see Ajax Listener module in the Tealeaf Web SDK.
Our environment for this release
- NPM 11.6.2
- Node 20.19.0
- macOS 26.0.1
Known issues
Session replay does not support inline frames inside the shadow DOM yet.
Released on November 3, 2025
Bug fixes
- Added the missing flushQueue module to improve screen capture on iOS devices during page unloads.
- Removed unnecessary console statements from non-debug builds.
- Added the ability to use a callback when invoking TLT.initLib and TLT.initLibAdv.
Improvements
None.
Our environment for this release
- NPM 11.6.2
- Node 20.19.0
- macOS 26.0.1
Known issues
Session replay does not support inline frames inside the shadow DOM yet.
Released on October 14, 2025
Bug fixes
Fixed an issue with Uncaught TypeError: t.publishOwnership is not a function in domCaptureService.
Improvements
None.
Our environment for this release
macOS 15.5
Known issues
Session replay does not support inline frames inside the shadow DOM yet.
Released on June 13, 2025
Bug fixes
We've fixed an issue due to which messages sent using the TLT.logCustomEvent API from a loop resulted in multiple identical messages rather than expected individual messages. The messages are now deeply cloned in order to get a unique object.
Improvements
None.
Our environment for this release
macOS 15.5
Known issues
Session replay does not support inline frames inside the shadow DOM yet.
Released on March 24, 2025
Bug fixes
Refactored code to remove the use of optional chaining to support ES5.1.
Improvements
Updated to the latest Ajax listener and also published it to the CDN.
Our environment for this release
macOS 14.5
Known issues
Session replay does not support inline frames inside the shadow DOM yet.
Released on February 14, 2025
Bug fixes
Fixed an issue with the Data Layer module having Uncaught Range Error: Maximum call stack size exceeded.
Improvements
We have added the support of cross-domain iframes and replay on a single page. To enable the new feature for your application, add the following to the parent page. Note missing open parenthesis and close parenthesis.
let config = window.TLT.getDefaultConfig()
// Must be enabled for cross-domain iframes
config.core.frames.enableCrossDomainCommunication = true
// Optional. If you want to whitelist a certain domain, use the following property. Otherwise the library will capture all the domains automatically.
config.core.frames.eventConsumer.childFrameHostnameWhitelist.push("WEBSITE.COM")
// Initialize the library with updated configuration
window.TLT.initLibAdv("YOUR APP KEY", "YOU COLLECTOR URL", config, true, true, true, true, true, undefined)
Then add the following to the child pages:
let config = window.TLT.getDefaultConfig()
// Must be enabled for cross-domain iframes
config.core.frames.enableCrossDomainCommunication = true
// In order to adjust path and IDs for data, indicate the ID of the iframe to be used on the parent page.
config.core.frames.eventProducer.producerId = "MYIFRAMEID"
// Initialize the library with updated configuration
window.TLT.initLibAdv("YOUR APP KEY", "YOU COLLECTOR URL", config, true, true, true, true, true, undefined
Our environment for this release
macOS 14.5
Known issues
Session replay does not support inline frames inside the shadow DOM yet.
Released on September 10, 2024
Bug fixes
- Google is deprecating the
unloadin Chrome and switching topagehide. We have adjusted the library to address this change. See related articles from Google: Deprecating the unload event, Legacy lifecycle APIs to avoid and Reenabling unload for a frame. - We fixed two issues in the Data Layer module. It is no longer preventing Google Tag Manager from sending events (such as clicks) to Google Analytics. The
TLT.logDataLayerAPI is logging type 19 messages correctly.
Improvements
- We added a new flag (
debugVoidElementsEnabled) for troubleshooting missing fonts in session replays. It enables DOM scanning for void elements with content inside to determine why the library cannot load a font. For example, the font may be placed inside the link element that is not supposed to have any content at all.
services: {
domCapture: {
captureDynamicStyles: true, // Default: false. This enables the capture of styles made using the CSS Object Model.
captureHREFStyles: true, // Default: false. This flag allows the SDK to capture styles inside a referenced CSS file. This flag should only be using for debug purposes or when the proxy server is not getting the CSS files correctly.
//The following 2 flags only work in the debug version of the SDK.
debugVoidElementsEnabled: true, // Default: false. This flag allows the SDK to scan the DOM for void elements with content inside. It only runs when the SDK is initialized
debugVoidElementsTimer: 10000 // Default: 10000. The time the SDK should wait in milliseconds before starting the scan.
}
}
- If a user’s browser has cookies and local storage disabled, the Tealeaf library is unable to capture sessions. We added alternative storage as a fallback option for cases like these. Use the
sessionIDUsesFallbackStorageparameter to enable the new feature.
config = {
modules: {
TLCookie: {
sessionIDUsesCookie: true, // Regular cookie flag, default true
sessionIDUsesStorage: true, // Regular storage flag, default false
sessionIDUsesFallbackStorage: true, // New alt storage flag, default false
}
}
};
Our environment for this release
MacOS 14.5
Known Issues
Session replay does not support inline frames inside the shadow DOM yet.
On March 11th, 2024, Acoustic introduced several improvements and bug fixes. This release is recommended for all Web SDK users.
Improvements
Added support for IE 11 and above.
Note:
Web SDK versions 6.4.72 and above will support IE11 and above only moving forward. IE9-10 will no longer be supported, and if you require the collection of session data from IE before version 11, you must use the previous versions of the web SDK.
Bug fixes
Fixed an issue supporting IE 11 due to the optional chaining operator.
Our environment for this release
MacOS 14.1
Known issues
Session replay does not support inline frames inside the shadow DOM yet.
Older entries
Updated 4 days ago