3D FlipBook - Compatibility Issue with 3D FlipBook jQuery Plugin on iOS 17

m***o@mybabbo.com
2024-05-23
2024-08-17

Hello Support Team,

I am writing to report an issue with the 3D FlipBook jQuery plugin. The plugin has been functioning correctly on iOS versions prior to 17. However, it appears to be broken on iOS 17, likely due to new privacy policies introduced in this version.

When accessing the plugin on a device running iOS 17, the console displays the following error:

Screenshot: https://ibb.co/p1B9dKJ

SecurityError: Sandbox access violation: Blocked a frame at "https://rd-plugins.bubbleapps.io" from accessing a cross-origin frame. The frame being accessed is sandboxed and lacks the "allow-same-origin" flag.

Additionally, there are errors related to DOMException, indicating issues with the current implementation under the new privacy constraints.

You can observe the behavior by visiting our demo page here: https://rd-plugins.bubbleapps.io/version-test/flip-book

This issue is affecting the functionality of the plugin and needs to be addressed to ensure compatibility with the latest iOS update.

Steps to Reproduce:

  1. Open the demo page on a device running iOS 17.
  2. Observe the errors in the browser console.
  3. Compare the functionality with devices running earlier iOS versions, where the plugin works correctly.

Expected Behavior: The 3D FlipBook plugin should function consistently across all iOS versions, including iOS 17, without any sandbox access violations or DOM exceptions.

Additional Information:

  • Browser: Safari on iOS 17
  • Platform: Bubble.io

Please let us know if there are any adjustments or updates required for the plugin to comply with iOS 17's new privacy policies.

Thank you for your assistance.

Best regards,

Replies

a***r@3dflipbook.net
2024-08-17
2024-08-17

Hi, it works fine on IOS 17. Probably on your site Content-Security-Policy disallows to use blob as frame source.

a***r@3dflipbook.net
2024-08-24
2024-08-24

In 1.16.1 we changed the plugin initialization, so it should work smoothly in Safari with any Content-Security-Policy.

Log In to leave a comment