Suggestion: Pause changing resolution while the Chatbox is in Focus

[sgtdeagle]

when the Logic triggers to change the resolution, while you typing in chat, the cursor loses Focus of the textbox and any input gets lost.

can you implement a automatic pause logic while the user active typing. like the Focus is on the textbox?

Plugin version 1.2.4

[FrozenCoTTon]

This also happens on Chrome

[Punshnut]

Thanks for the detailed report, @sgtdeagle - and good to know it reproduces on Chrome too, @FrozenCoTTon!

This is fixed in v1.2.14. The enforcement logic now checks document.activeElement before touching any player UI. If a text input or the chat box (Twitch uses a contenteditable div) currently has focus, the quality change is silently skipped and automatically rescheduled ~1.5 seconds later - so the correct quality still gets applied shortly after you finish typing, without interrupting your message.

The fix covers all input types: the chat box, search fields, and any other text input on the page.

The update will be live soon. Let me know if you run into anything else! 🙂

[FrozenCoTTon]

Thank you @Punshnut

Question regarding it checking every few seconds: Does it use a lot of CPU by constantly checking like that or it is minuscule?

[Punshnut]

The CPU impact is essentially zero during normal use.

The extension is purely event-driven: it only wakes up when something meaningful happens. A setting changes, the URL navigates, the tab gains focus, the page loads. No background loop constantly crawling your DOM.

The one lightweight interval that does run is a URL watcher that fires every second and does nothing but compare two short strings to detect Twitch SPA navigation. A negligible handful of instructions, gone in microseconds.

Once quality is confirmed, the extension enters a 25-second trust window where it skips menu detection entirely. Even if a trigger fires during that window, it bails out immediately without touching anything.

And isUserTypingInInput() itself? A single document.activeElement read. One property lookup, no loops, no DOM traversal. It only runs at the very start of an enforcement pass that's already behind cooldowns, debounces, and that trust window, so in practice it fires a handful of times per session at most.

Short version: completely negligible. You won't feel it. 🙂