Integrations where the video.js player is in an iframe with a different origin are throwing errors when findUspApiLocatorWindow attempts to locate an ancestor frame with ancestor.frames.__uspapiLocator.
No error is thown:
if the ancestor is same origin and a __uspapiLocator frame does not exist
if the ancestor is not same origin but a __uspapiLocator locator frame exists
To remedy, we can wrap attempts to read ancestorFrame.__uspapiLocator in a try / catch. There is no need to handle the error as
a) we'd expect to run into this while traversing multiple cross domain ancestors and
b) if we don't find one in the top window, it probably just means there's no CMP. Users can't control whether this runs or not, so a warning or error would just be clutter.
Integrations where the video.js player is in an iframe with a different origin are throwing errors when
findUspApiLocatorWindowattempts to locate an ancestor frame withancestor.frames.__uspapiLocator.No error is thown:
__uspapiLocatorframe does not exist__uspapiLocatorlocator frame existsTo remedy, we can wrap attempts to read
ancestorFrame.__uspapiLocatorin a try / catch. There is no need to handle the error as a) we'd expect to run into this while traversing multiple cross domain ancestors and b) if we don't find one in the top window, it probably just means there's no CMP. Users can't control whether this runs or not, so a warning or error would just be clutter.