Native Event Access in "Run JavaScript" Interactions

It would be great having feature that exposes the native browser event object within Replo’s On Click → Run JavaScript interactions to allow developers to access critical data like event.target.

Currently, because this object is inaccessible, users struggle to isolate JavaScript actions when a page contains multiple identical or duplicated sections, such as in A/B testing scenarios.

By allowing the script to identify exactly which element was clicked, developers could use simple logic like .closest() to ensure actions are "siloed" to the correct container, preventing accidental triggers in hidden or duplicated sections.

Implementing this change would eliminate the need for cumbersome global event listeners in Custom HTML blocks and enable the creation of truly portable, "smart" components that function reliably regardless of where they are placed on a page.