emscripten-core/emscripten

Integrate emrun with noInitialRun / INVOKE_RUN=0

Open

#11,448 opened on Jun 19, 2020

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C++ (3,519 forks)batch import
good first bughelp wanted

Repository metrics

Stars
 (27,361 stars)
PR merge metrics
 (Avg merge 19d 10h) (147 merged PRs in 30d)

Description

Some "powerful" Web APIs are only allowed in response to user interaction (e.g. click on a button) somewhere on the call stack.

In these cases, it's useful to avoid running Emscripten automatically, and instead invoke it manually in response to such allowed user interaction.

noInitialRun / INVOKE_RUN=0 allow to build code like this, but they're not very convenient to use with the autogenerated HTML and emrun helper during testing and development, because it will simply open HTML and the only way to run the code is to open DevTools and call callMain manually.

I propose that that, when code is compiled in such mode, HTML would be generated with a simple "Run" button which will invoke callMain on click with command-line arguments from GET params just like in a regular build with auto-run.

Contributor guide

Research direction
Examine the emrun script and the HTML template used for Emscripten output. Identify where the 'Run' button should be added and how to conditionally include it based on the noInitialRun setting. Also check existing documentation for INVOKE RUN=0.
Tech stack
ccpp
Domain
frontenddeveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
CC++Emscriptenemrun
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45