CHANGED - OPTIONS PAGE TAGLINE
- options.html's tagline under the logo/title (.tagline, previously "AI
spellcheck for the web") now reads "AI Spell Checker & Corrector",
matching v2.3.13's renamed extension name.


CHANGED - EXTENSION NAME
- manifest.json's "name" field: "TypoGuard - AI Spell Check & Correction" ->
"TypoGuard - AI Spell Checker & Corrector". This is the name shown in
chrome://extensions, the Chrome Web Store listing, and Firefox's
about:addons -- action.default_title (the toolbar hover tooltip,
"TypoGuard - AI Spell Checker") is a separate string and was left as is.


REVERTED - V2.3.10'S BLUR/REFOCUS SPELLCHECK CACHE-BUST -- DEGRADED TYPOGUARD'S OWN CHECKING ON OUTLOOK WEB
- User accepted native + TypoGuard double-underlining as a reasonable
trade-off on Outlook Web rather than continuing to chase full native
spellcheck suppression, but reported that TypoGuard's own (Gemini-based)
checking had gotten noticeably worse in the same session: the console
showed a flood of "Text changed since request, re-triggering check"
cycles firing mid-typing, well beyond what normal debounced typing
produces.
- Root cause: __forceSpellcheckRefresh() (added in v2.3.10 to fight a
Chromium caching quirk) calls el.blur(); el.focus(); on the field
whenever __applySpellcheckOverride first touches it. That synthetic focus
event re-enters this same file's own focus listener, which calls
__setCheckedText(target, null) and __scheduleCheck(target) -- exactly as
if the user had just tabbed into the field -- discarding whatever text
was already checked and forcing an immediate re-check. On Outlook Web,
where v2.3.11 additionally started overriding document.activeElement
itself, this fired on every such element the override newly reached,
compounding into the flood observed.
- Removed the blur()/focus() body from __applySpellcheckOverride (and the
now-unused __forceSpellcheckRefresh function/its selection-preserving
logic) entirely. Left everything else from v2.3.9-v2.3.11 in place --
setting the spellcheck attribute itself, __watchSpellcheckAttribute's
defensive re-assertion, and __maybeOverrideActiveElementSpellcheck's extra
attribute-only override of document.activeElement -- since none of that
touches focus or fires events.


BUG FIX - V2.3.10'S BLUR/REFOCUS REFRESH NEVER ACTUALLY RAN ON OUTLOOK WEB -- WRONG ELEMENT CHECKED FOR FOCUS
- User re-tested v2.3.10 live: identical result, native "Ορθογραφία" spelling
context menu with real suggestions still appeared on right-clic