Impossible to enter VR from this morning, ~ 9 AM CET
Post by iconPost by Retsam | 2021-01-05 | 10:03:40

It looks like serious 'update' is ongoing and VR messed up, like always. Chrome console reports:

JQMIGRATE: Migrate is installed, version 1.4.1
p24.js:354 Uncaught (in promise) TypeError: Cannot read property 'url' of null
at p24.js:354
(anonymous) @ p24.js:354
p24.js:13 Uncaught DOMException: Blocked a frame with origin "" from accessing a cross-origin frame.
at new P24ContentScript (chrome-extension://aiicmmpkicnndkhlnnloilpgncbpkbjj/src/assets/js/p24.js:13:29)

People does report many connection problems in VR Lounge and point at lack of support. Currently I could not report it to VR (it would be also useless), as interface to do that is not available at all. It looks like 12 year of experience of VR (from programming point of view) brings no lesson to that VR business.

commenticon 1 Comment
Post by iconPost by brizeljohn | 2023-01-10 | 07:08:02
This error "Blocked a frame with origin from accessing a cross-origin frame " is not a bug. The same-origin policy is a security mechanism that ensures that window objects only have access to the informations they are authorized to get.

The window.postMessage() method provides a controlled mechanism to securely circumvent this Same-Origin Policy restriction. The window.postMessage() safely enables cross-origin communication between Window objects; e.g: between a page and an iframe embedded within it.

postMessage(message, targetOrigin)
postMessage(message, targetOrigin, [transfer])

targetOrigin - specifies what the origin of targetWindow must be for the event to be dispatched, either as the literal string "*" (indicating no preference) or as a URI.
Topics list
Copyright 2009 by ZEZO.ORG. All Rights Reserved.