Bug 515384 - User Story Improve Default Action Behavior in Dialog
Summary: User Story Improve Default Action Behavior in Dialog
Status: REPORTED
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface & Miscellaneous (other bugs)
Version First Reported In: 25.12.1
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-02-01 13:06 UTC by Jeffrey Krebs
Modified: 2026-02-01 13:06 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeffrey Krebs 2026-02-01 13:06:47 UTC
Here is a link to my development user story in my Google Docs.
for proper formatting.
https://docs.google.com/document/d/1foVl0C7ZvcNt6VI-L2yIsLCmSOGp97zR4fhmJRIAM8g/edit?usp=sharing

Here is the direct details non-formatted
User Story
As a video editor working in Kdenlive,  
I want the default action in dialog boxes to be the affirmative option (Save/OK/Accept),  
so that pressing 
Enter confirms my work instead of Ignoring or discarding it, reducing the risk of losing changes in some cases and improving workflow efficiency.
Additionally using a manual mouse close on title tool, does not warn that you are about to lose modifications to an existing title.
Problem Statement
Pressing Enter currently triggers Cancel in some dialogs.
This leads to:
Lost work 
Confusion and frustration.
A break from expected UI behavior across KDE/Qt applications.
Reduced keyboard‑driven efficiency.

Users expect Enter to confirm, not discard their work.
Why This Matters
 Editors often work quickly and rely on muscle memory.
 Kdenlive is used in professional and semi‑professional environments where speed and reliability matter.
 Accidental cancellation is a high‑impact UX failure because it can destroy user input.
 Aligning with KDE HIG and Qt UX norms improves consistency and predictability.
Scope
This story applies to all dialog boxes where:
 There is a clear affirmative action (e.g., Save, OK, Apply, Accept).
 There is a Cancel or Close option.
 The dialog is modal and expects a user decision.
Examples include:
 Title Tool (for manual close)
 Project Settings dialogs
 Effect configuration dialogs
 Save/Discard prompts
 Any modal editor or tool with OK/Cancel buttons
Acceptance Criteria

1. Default Button Behavior
 The affirmative action button (e.g., OK, Save, Accept, Apply) must be the default button.
 Pressing Enter/Return must trigger the affirmative action.
 Pressing Esc must trigger Cancel, as expected.
2. Visual Indication
 The default button must be visually indicated according to KDE/Qt standards (e.g., highlighted or with a default focus ring).
3. Consistency Across Application
All modal dialogs must follow this rule unless there is a compelling, documented exception.
No dialog should default to Cancel unless:
The dialog is destructive by nature (rare), and
KDE HIG explicitly recommends Cancel as default (unlikely).
4. Regression Testing
 Verify that no existing workflows break due to the change.
 Confirm that keyboardonly navigation behaves predictably:
 Tab cycles through buttons.
 Enter activates the default affirmative action.
 Esc cancels.
5. Title Tool Specific Fix
The Title Tool must no longer discard user work close box is used without warning
Enter should default to update title
Esc Key should default to Cancel
Tab Key should be access save or cancel, at the moment it cycles to every function except the save or cancel