Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standalone slingcode.html unable to launch apps #90

Open
bryan-lott opened this issue Jun 24, 2020 · 3 comments
Open

Standalone slingcode.html unable to launch apps #90

bryan-lott opened this issue Jun 24, 2020 · 3 comments

Comments

@bryan-lott
Copy link

Hi, I'm unable to launch an app from slingcode if I download the slingcode.html file and run it locally. After clicking on the launch button for (for instance) Hello World, I just get a blank screen with no app. Running it from slingcode.net/slingcode.html works as expected. In addition, after I've opened the blank screen/no app, if I then edit the app, the stop button shows but doesn't seem to work
Tried on both Chrome and Brave.

The console for the app edit screen when clicking on the stop button gives the following output:

VM5 slingcode.html:1 Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('null') does not match the recipient window's origin ('null').
(anonymous) @ /C:/Users/mysti/OneDrive/Desktop/slingcode.html?app=c87e1e4a-f9f0-49e2-bcef-b3e7a2b1a8f9:1
Ig @ VM5 slingcode.html:1
c @ VM5 slingcode.html:1
t @ VM5 slingcode.html:1
(anonymous) @ VM5 slingcode.html:1
u @ VM5 slingcode.html:1
(anonymous) @ VM5 slingcode.html:1
r @ VM5 slingcode.html:1
J @ VM5 slingcode.html:1
K @ VM5 slingcode.html:1
ee @ VM5 slingcode.html:1
ae @ VM5 slingcode.html:1
Xr @ VM5 slingcode.html:1
m @ VM5 slingcode.html:1
be @ VM5 slingcode.html:1
ve @ VM5 slingcode.html:1
l.unstable_runWithPriority @ VM5 slingcode.html:1
Ct @ VM5 slingcode.html:1
h @ VM5 slingcode.html:1
(anonymous) @ VM5 slingcode.html:1
/C:/Users/mysti/OneDrive/Desktop/slingcode.html?app=c87e1e4a-f9f0-49e2-bcef-b3e7a2b1a8f9:1 Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('null') does not match the recipient window's origin ('null').

The console for the blank screen gives the following output:

Invalid asm.js: Expected function name
slingcode.html?app=c87e1e4a-f9f0-49e2-bcef-b3e7a2b1a8f9:1 CodeMirror includes: {} {} {} {}
slingcode.html?app=c87e1e4a-f9f0-49e2-bcef-b3e7a2b1a8f9:1 can-make-files? true
slingcode.html?app=c87e1e4a-f9f0-49e2-bcef-b3e7a2b1a8f9:1 can-p2p? true
slingcode.html?app=c87e1e4a-f9f0-49e2-bcef-b3e7a2b1a8f9:1 main!
slingcode.html?app=c87e1e4a-f9f0-49e2-bcef-b3e7a2b1a8f9:1 reload!

Happy to help however I can!

@chr15m
Copy link
Owner

chr15m commented Jun 25, 2020

@bryan-lott perfect, thanks for all the detail here. I have replicated this issue and will fix. 👍

@chr15m chr15m added the bug Something isn't working label Jun 25, 2020
@chr15m chr15m added this to To do in 2nd release via automation Jun 25, 2020
@chr15m
Copy link
Owner

chr15m commented Jul 8, 2020

Note to self: investigating this further new versions of Chrome are blocking access to MessageEvent.source object. A potential workaround is to ask the destination frame to do the re-rendering itself with a postMessage, rather than trying to push directly into the window.

@adisetiawan
Copy link

just FYI: Latest Firefox works fine

@chr15m chr15m moved this from To do to In progress in 2nd release Jul 16, 2020
@chr15m chr15m removed this from In progress in 2nd release Aug 17, 2020
@chr15m chr15m added this to In progress in Current dev Aug 17, 2020
@chr15m chr15m moved this from In progress to To do in Current dev Jan 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

3 participants