There is no "start of the code" other than the time when the JavaScript
is parsed. But as JavaScript can be in multiple places (e.g. included in
script tags somewhere in the page) and even be added at run time, it is
not clear, what would need to be evaluated again and what not. Also the
page may be in a different state from what it was originally in the
beginning, so without reloading the page, your code would meet
preconditions it did not expect.
From your StackOverflow-question:
"Given the |keydown| event is triggered only once, I consider sending
the interpreter back to the start after the |keydown| event was
triggered disposably, and without refreshing the page (Sorry if it seems
absurd, I'm new to JS and failed finding the source of the bug)."
You may use the debugger and set a breakpoint to find your bug.
On 06.09.2017 05:00, Benqzq wrote:
Please consider adding a `stop` command.
A `stop` command tells a JS interpreter "Go back to the start of the
code".
When an event is triggered, he interpreter will run again, until the stop.
This can be useful in this particular case
<https://stackoverflow.com/questions/46042185/sending-a-javascript-interpreter-back-to-the-top-of-your-code>.
--
בשאיפה לעולם שמח יותר לבני אדם וחיות כאחד,
Aspiring for a happier world for humans and animals alike,
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
--
Michael Kriegel • Head of R&D • Actifsource AG • Haldenstrasse 1 • CH-6340 Baar
• www.actifsource.com • +41 56 250 40 02
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
