Kleopatra: Saving/restoring column layout in certificate lookup doesn't work
Closed, ResolvedPublic

Assigned To
Authored By
• ikloecker
Mar 22 2024, 3:17 PM

Description

How to reproduce:

  • Open "Lookup on Server"

Observation: All columns in the (empty) list view have the same (default) width. Okay on first opening.

  • Search for "foo". You should get some results.
  • Enable the Origin column (or some other column).

Observation: The columns are adjusted to the content. I think that's okay.

  • Close dialog. Then open it again.

Observation: All columns have the same width. Could be considered okay or not.

Alternatively to saving/restoring the column layout it would be okay for me if the columns are adjusted to the content after setting the result. Maybe that's even better than restoring a fixed column layout because the needed column widths depend on the results.

Event Timeline

• aheinecke added a subscriber: • aheinecke.

I agree with the column save /restore but i disagree with adjust to contents since this can create a "jumpy" layout e.g. with long comments and the user might be annoyed if she changed thr layout and it is then automatically changed again

• TobiasFella moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Apr 3 2024, 10:37 AM
• TobiasFella changed the task status from Open to Testing.Oct 2 2025, 12:45 PM
timegrid edited projects, added gpd5x; removed Restricted Project.Dec 12 2025, 2:42 PM
timegrid moved this task from Backlog to QA on the gpd5x board.
• ebo moved this task from QA to Done on the gpd5x board.
• ebo added a subscriber: • ebo.

Gpg4win-5.0.0-beta476

Adding a new column to the layout is now remembered.
The with of the newly added column (Key-ID, all others are shown by default) is not set to the width of the content. But I think that is ok, one can increase the width manually and that is then remembered.