Improve DOM safety checks for post body enhancements, especially for iOS Safari #507
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes ECENCY-NEXT-VM6. The issue was that: iOS Safari's strict cross-origin policies block iframe video embeds, causing DOM elements to be null, leading to
TypeErrorwhen accessed.isElementSafefunction to check if the post body element is safe to access, including handling potentialSecurityErrorexceptions in iOS Safari due to cross-origin iframe restrictions.null is not an objecterrors andSecurityErrorexceptions, to aid in debugging.isConnectedproperty is checked safely, with a fallback mechanism if the check fails due to security restrictions.This fix was generated by Seer in Sentry, triggered automatically. 👁️ Run ID: 29630
Not quite right? Click here to continue debugging with Seer.