Identify the intended list operation
Before dragging files into Haruna, decide whether they should join the existing list or replace it. Preserve any important playlist through its supported save route. A successful drop with the wrong scope can look like lost entries even when the application performed its configured action.
Use a disposable three-file example: two recognizable clips form the starting list and a third is the candidate addition. Keep those files in a known local folder. This makes the expected append or replacement result visible without depending on a long viewing session.
Check the installed release’s documented behavior
KDE’s Haruna release notes describe a video-area split introduced in the 1.5 series: one region appends while another replaces the default playlist. Check the actual installed version and visible target. Older screenshots may not represent the current interaction.
Keep the playlist visible during the first gesture and read which item is active. A drop target and an automatic sibling-file setting can both affect the resulting list. Preserve their current states rather than interpreting every additional file as an accidental duplicate.
Compare one drop scope at a time
Perform the intended addition and inspect the resulting entries before starting playback. Record where the file was released. If replacement is also being tested, use a separate saved or disposable list so the original arrangement remains recoverable.
Open the selected item and confirm it is the intended source. A correctly populated list and a playable file are different checkpoints. If a file moved between the drag and the open action, retain that fact as an access issue rather than blaming the list operation.
Check ordinary reopening behavior
After a deliberately saved session, reopen through the actual workflow you intend to use and inspect the active list. Keep the launch context—opening the application alone versus opening it with a file—attached to the result. The KDE notes document playlist-startup changes between releases.
The expected outcome is a predictable list edit for the installed build. It does not copy the media, guarantee every network URI remains reachable or prove permanent storage of an unsaved session. Retain the version and exact drop region if the result differs from the current documented behavior.
Questions answered
Why should I record the drop region?
The documented interaction can use different regions for append and replacement. The gesture target is part of the reproduction.
Does a successful list edit create a media backup?
No. Keep the original files protected and verify their actual access separately from playlist arrangement.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.