Confirming that this is still an issue. I'm using repl.it to host an Hour of Code starter project, and I had to create special notes about how to fork it and manually refresh the page to ensure the embedded results panel displays the results of the new fork and not from the original.
The two attached photos show the starter repo before forking, then after clicking fork and doing nothing else AS A NON-USER (this may be important?). The rest of the page refreshes automatically, but the results panel does not, hence retaining the url of the original project.
You can see the 2 slides I made with how-to instructions and image here if that helps: https://docs.google.com/presentation/d/1je6xs0PfevSTPAdDWoZu50pmOn0BvpflTHH1fhQt2t4/edit#slide=id.g7ab7505153_0_499
I believe this happens if you rename your new repl to be that of your old repl - this is definitely a bug still at large and a tricky one at that. Renaming it to be something unique should fix this as a stop gap.
I experienced something similar recently. I forked a "HTML, CSS, JS" repl, and shared the fork for the challenge. The embedded repl showed the scripts from the fork, however it ran the original script. I ended up deleting the fork, and using a separate repl to use it as a fork.
@AkhilGupta: If you see this again, could you contact us and tell us the URLs for the two repls? I haven't been able to reproduce this.
@Maka: If I ever come across this again, then yes, surely. Will probably create a test repl or something for it.
Oh, I didn't mention this earlier, but I was also fiddling a lot with the repl names. And iirc, I even swapped the original and fork's name a few times, before I noticed this.
Odd. For me my changes neither show in the results nor the console but they do in a new tab.
Uh, I'm running into this now 10 MONTHS after the dates on this post and comments.
we're fixing this, @Faris can you please have a look?
@Haya: just wanted to see if you have any updates. I work at Thinkful and we use replit to teach people to code, and we're still getting reports of this bug from our students.
This has been fixed for a long while :)