You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way these ad blockers typically work is blocking the URL pattern to the recording script fs.js. It would be useful to have even a naive timeout on whether FS is ever loaded into the window. Another use case is content-security-policy that could also block fs.js. Thanks for bringing it up.
@van-fs - Yup - the ad block hook I demonstrated above just tries to request the script and when it fails it handles the exception. This of course causes duplicate calls ( though cached ) so it would be grat to handle this in the lib itself.
Problem
If a user is using a ad blocker, sometimes it will not start up fullstory. I would like the ability to catch if the error occurs and handle it.
Proposal
You could do something like make
Fullstory.init
return a Promise and error if it fails, so you could do:The text was updated successfully, but these errors were encountered: