One of the two commits after 2v24.118 changes the behavior so the menu's touch listener runs even though it wasn't registered at the time of the touch event. My guess is it has to do with the menu being called from within the touch listener that first act on the event.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Edit: Spoke too soon. See next comment.
I narrowed it down.The bug doesn't appear on fw 2v24.118:https://www.espruino.com/binaries/travis/f415a9f0b264ead525ea903f99b27441d7b1793f/But does appear on the next compiled one, 2v24.120:https://www.espruino.com/binaries/travis/10b6f5fe54de6697866a8b22d8d9948c05df5302/
One of the two commits after 2v24.118 changes the behavior so the menu's touch listener runs even though it wasn't registered at the time of the touch event. My guess is it has to do with the menu being called from within the touch listener that first act on the event.So either:https://github.com/espruino/Espruino/commit/445d331de3d9d035a3da86dc9583b899da2479bb
(I suspect this one)orhttps://github.com/espruino/Espruino/commit/10b6f5fe54de6697866a8b22d8d9948c05df5302 .