Fix race loop bug and button styling in Réseau de tri#372
Conversation
…e button - Fixed an issue where `btnStartRace` was bound twice, leading to multiple `startRace` calls. - Tracked both `raceInterval` and `raceTimeout` and ensured they are properly cleared when starting a new level. - Fixed the button design for "Valider l'étape" by ensuring it uses the core `.btn` class alongside `.btn-primary`. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
reseau_de_tri.htmlwhere clicking the "Lancer la course !" button would trigger the race multiple times due to a duplicate event binding, leading to an infinite race loop that cascaded into new levels.setIntervaland the resetsetTimeoutspecifically so they can be reliably canceled during transitions to a new level..btnclass to.btn-primaryfor the "Valider l'étape" button to match the platform's standardized UI styling and properly display padding and borders.PR created automatically by Jules for task 12605931378533159579 started by @Animation-EdNum