This month, we’re spotlighting creative ways community members are experimenting with Rise 360’s new Code Block (Beta) feature. From quick prototypes to full mini-games and simulations, these project...
Updated 2 months ago
Version 1.0
Blog Post
I'd be curious to know what evidence they're using to say Rise is stripping out code, whatever that means. Their output depends entirely on their input.
Here's an example I made recently that was copied and pasted whole-cloth from Copilot to a Rise code block, and it ran perfectly with only personal style changes.
so the button functions were working and then they'd stop randomly. Gemini gave me this feedback:
"I apologize for that! If the "Show Hints" interaction—which relies on the CSS Checkbox Hack—isn't working, it means the Articulate Rise environment is likely blocking the necessary advanced CSS selectors needed for that trick to function.
The CSS Checkbox Hack relies on the sibling selector (~) and the :checked pseudo-class to reveal content without JavaScript:
CSS
#hints-toggle:checked ~ .hints-container { display: block; }
If this is failing, the platform is likely stripping or ignoring that complex rule.
Since both the JavaScript Button and the CSS Checkbox Hack are now confirmed non-functional in your environment, the only reliable way forward is to remove all interactive buttons and revert the hints to permanently visible text within a designated area."
It appears it was wrong but i dont have an explanation for why the button would work and then stop. I know vibe coding isnt very exact all the time but i was working on this for hours. Happy to be wrong!