From: Denis Benato <denis.benato@linux.dev>
To: "Manuel A. R. de Orúe Ríos" <deor001@gmail.com>,
linux-kernel@vger.kernel.org, luke@ljones.dev,
platform-driver-x86@vger.kernel.org
Subject: Re: Dolphin (26.08.0): "Expandable" folders in Details view not working when per-folder view properties are enabled
Date: Wed, 9 Sep 2026 19:18:23 +0200 [thread overview]
Message-ID: <81e59a58-5691-4959-aa3b-2b9728349ddb@linux.dev> (raw)
In-Reply-To: <CAOXykpgCPMB7fGGJXD0wdx-0boy3vdRZraFRhegrh7azJiYONA@mail.gmail.com>
On 9/7/26 03:11, Manuel A. R. de Orúe Ríos wrote:
> Hello, Denis and Luke.
Hello Manuel!
> I was wondering if you could help me communicate about, and get some
> information regarding, the following topic:"
> in Dolphin it's intentional (a design decision) or an oversight that
> hasn't been addressed yet.
>
> Environment:
> - Dolphin 26.08.0
> - Fedora 44, KDE Plasma 6 (Wayland)
>
> Steps to reproduce:
> 1. In Configure Dolphin -> View -> Details tab, enable "Folders: Expandable".
> 2. In Configure Dolphin -> General -> Behavior, enable "Remember
> display style for each folder" (i.e. GlobalViewProps=false).
> 3. Open any folder in Details view.
>
> Observed result:
> The expand arrows for subfolders (the inline tree view) do not appear,
> even though "Expandable" is checked globally.
>
> Expected result:
> The expandable folder tree should work regardless of whether view
> properties are set globally or remembered per folder, since
> "Expandable" is configured as a global Details-view setting and is not
> something exposed as part of the per-folder properties.
>
> This looks related to Bug 524626, which reports a similar coupling
> issue in 26.08.0: the new per-folder zoom feature is tied to
> per-folder view properties (GlobalViewProps=false) with no way to keep
> it independent. My case seems to be the same underlying pattern — a
> setting that should logically be independent from the
> global/per-folder view-properties toggle ends up depending on it.
>
> Could you let me know whether this is expected/by design, or if it's a
> gap that hasn't been considered yet? Happy to provide more details,
> logs, or test further if useful.
Sorry but I don't use said features, and this is the linux kernel mailing list
so... Not the correct place to get answers about this.
You should try KDE's own forum: https://discuss.kde.org/ or the KDE bug
tracker: https://bugs.kde.org/index.cgi
> Regards,
> Manuel de Orúe Ríos.
> ___________________________
Anyway best of luck with solving this issue!
Best regards,
Denis B.
prev parent reply other threads:[~2026-09-09 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 1:11 Manuel A. R. de Orúe Ríos
2026-09-09 17:18 ` Denis Benato [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81e59a58-5691-4959-aa3b-2b9728349ddb@linux.dev \
--to=denis.benato@linux.dev \
--cc=deor001@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®