[dolphin] [Bug 432530] New: Files with long filename not behaving properly

[Apurv]

https://bugs.kde.org/show_bug.cgi?id=432530

            Bug ID: 432530
           Summary: Files with long filename not behaving properly
           Product: dolphin
           Version: 20.12.1
          Platform: Debian unstable
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: view-engine: icons mode
          Assignee: dolphin-bugs-null at kde.org
          Reporter: appjoe.beta at gmail.com
                CC: kfm-devel at kde.org
  Target Milestone: ---

Created attachment 135436
  --> https://bugs.kde.org/attachment.cgi?id=135436&action=edit
screenshots of settings and bug

SUMMARY
For a file with long filenames and icon-view settings set at max 2 lines,
overflows file extension to another (stray and undesired) line.

And if a directory is opened in the directory containing long filenames, file
extensions are visible in the directory for some time.

P.S. - compositing is enabled (even if it might not be obvious in screenshots
attached)


STEPS TO REPRODUCE
1. View mode config:
      Label-width: medium
      Maximum-lines: 2
2. create a directory containing directory & files with a long name and an
extension at the end (tested with: "foldername name with really long text that
needs to be stripped.txt")
3. Now open the directory within directory (blank area in dolphin will show
"txt" labels)

OBSERVED RESULT
For step 2: file extension will overflow onto the third line ignoring the
"max-lines: 2" settings for dolphin,

For step 3: stray file extensions are visible from last screen


EXPECTED RESULT
filenames shouldn't exceed the max lines set in settings.
dolphin's view should be cleaned before displaying contents of a new directory.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are on the CC list for the bug.