That’s a good question! We ultimately decided to nest the webpage and YouTube CoBlocks into their own click-events as to prevent misuse of these features, as well as to comply to web browser security standards (e.g. external links should always be opened by active user input, never programmatically). This helps us avoid cases where a user creates code that would, for example, open several hundred tabs.
About your request @tajajtsidi, we’ll look into possibilities for this kind of behavior with our developers. There are certainly use-cases where stopping the scene would make sense, but so are also situations where you’d like to keep background music playing or program behavior to happen in the background while the user is focussing on the YouTube link or opened website.