https://bugs.kde.org/show_bug.cgi?id=528342
Henrique Sant'Anna <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |usability --- Comment #8 from Henrique Sant'Anna <[email protected]> --- I respectfully disagree with closing this as NOT A BUG, as this conflates an internal implementation detail (QFont bundling family and size together in the local config) with the user's actual intent and mental model. 1. Zoom is a viewport state, not a "temporary font configuration": When a user triggers zoom via a gesture or shortcut (Ctrl+MouseWheel or Ctrl++/Ctrl+-), they are adjusting a view state (magnification), not overriding the typography configuration of that tab. In fact, Kate does not even expose a UI feature to set a per-tab font family. Treating a zoom gesture as an explicit override of the font family leaks how KTextEditor internally stores QFont directly into the user experience. 2. Changing the font in Settings has a clear expectation of immediate visual feedback: Unlike zooming, opening Settings → Configure Kate → Appearance, selecting a new Editor Font, and clicking Apply is an explicit configuration action. The user does this specifically intending to see their currently open code rendered in the newly selected font. When clicking Apply produces zero visual feedback on the active tab, simply keeping the old font family silently, it directly frustrates the user's expectation and looks indistinguishable from a bug. To put this in perspective from a UX standpoint: Is there any realistic scenario where a user changes the font family in Settings, clicks Apply, and actually expects or wants the currently active tab NOT to apply the new font family? 3. No "error-prone heuristics" are required: Supporting the expected behavior does not require guessing user intent or building complex heuristics, it only requires deterministic state handling: After Ctrl+0 (Reset Font Size): Even under the premise that a temporary modification overrides persistent settings, once the user presses Ctrl+0 to reset the zoom back to 100%, there is no temporary modification active anymore. Having a tab that is at 100% default zoom permanently ignore future global font changes for the rest of the session breaks even that premise. Even while zoomed in/out: Zoom only affects font size/scale, never font family. Updating the font family across all open views when the global font family changes (or storing zoom as a relative factor/delta rather than a static QFont copy) is completely deterministic and requires zero heuristics. -- You are receiving this mail because: You are watching all bug changes.
