Conversation
This adds a history tracking mechanism to orchestrator.ts. When the system detects that an element is oscillating back and forth between two measurements in an A->B->A pattern, it skips applying the styles and breaking the infinite loop. This prevents infinite ResizeObserver triggers. Co-authored-by: BALOTIAS <13562297+BALOTIAS@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
Fixes the Measurement/CSS feedback-loop guard issue described in the README where line count flips forever between two states. We now track the latest measurements per element and prevent
applyResultandrecordMeasurementif a repeating sequence is detected.PR created automatically by Jules for task 12603870675343980741 started by @BALOTIAS