[kwin] [Bug 474945] Single clicking the top of the chromium window while it is left or right snapped causes it to jump to the middle of the screen

2023-09-27 Thread Payton Q
https://bugs.kde.org/show_bug.cgi?id=474945

--- Comment #1 from Payton Q  ---
Created attachment 161915
  --> https://bugs.kde.org/attachment.cgi?id=161915=edit
Behavior

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 474945] New: Single clicking the top of the chromium window while it is left or right snapped causes it to jump to the middle of the screen

2023-09-27 Thread Payton Q
https://bugs.kde.org/show_bug.cgi?id=474945

Bug ID: 474945
   Summary: Single clicking the top of the chromium window while
it is left or right snapped causes it to jump to the
middle of the screen
Classification: Plasma
   Product: kwin
   Version: 5.27.7
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-window-management
  Assignee: kwin-bugs-n...@kde.org
  Reporter: pmqui...@proton.me
  Target Milestone: ---

SUMMARY

(See attachment)
Single clicking the top of the chromium window while it is left or right
snapped causes it to jump to the middle of the screen

STEPS TO REPRODUCE
1. open chromium
2. snap it to the left or right
3. single click the top of chromium while it's snapped
4. it jumps to the center

OBSERVED RESULT
Chromium jumps to the center

EXPECTED RESULT
Nothing should happen

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.106.0
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio-extras] [Bug 443806] Dolphin should allow option to cache thumbnails for separate encrypted devices / locations

2023-05-22 Thread Payton Q
https://bugs.kde.org/show_bug.cgi?id=443806

--- Comment #35 from Payton Q  ---
Git commit 231668fb984fb1e7269a313bb7688c7473497f47 by Payton Quinn.
Committed on 22/05/2023 at 18:15.
Pushed by ngraham into branch 'master'.

Enable thumbnail caching if thumbnail directory is on an encrypted volume

M  +8-1src/gui/previewjob.cpp

https://invent.kde.org/frameworks/kio/commit/231668fb984fb1e7269a313bb7688c7473497f47

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio-extras] [Bug 443806] Dolphin should allow option to cache thumbnails for separate encrypted devices / locations

2023-05-15 Thread Payton Q
https://bugs.kde.org/show_bug.cgi?id=443806

--- Comment #32 from Payton Q  ---
I think the reason for the disconnect here is that there are two different use
cases:

Some people use encrypted drives in a static fashion. As in, it's always
attached to their machine.

Other people use encrypted drives in a more "moveable" fashion. As in, it's
either an encrypted volume that they can move around (as in KDE Vaults), or
it's a portable drive they take with them to other machines.

For the first group, if the home directory is encrypted, then there's no
downside to storing the thumbnails in the usual location in the homedir.
However, there would be a downside to storing them on the separate drive, for
the reasons listed above.

However, for the second group, it's the exact opposite. For people who use
their encrypted volumes in a portable manner, storing the thumbnails on the
drive itself has no downsides. If the freedesktop spec was updated to permit
it, then any other compliant machine they take their drive to would check on
the drive itself to look for thumbnails. However, storing them in the homedir
would have a downside, as the thumbnails would need to get regenerated every
time the drive is used on a new machine.

The problem is that based on the thumbnail spec provided to me by Nate, what
the first group is advocating for is compliant with the existing thumbnail
spec. I suggest that we go ahead with the fix I proposed on my merge request.
Namely, for any encrypted volume whatsoever, if the homedir is encrypted, store
the thumbnails in the homedir per the spec. Then, if we want to pursue a change
to the spec, we can have that conversation separately. In the meantime, I don't
think it's fair for kde users nor is it a good look for kde to remain
noncompliant with the spec and leave users without basic functionality for so
long.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio-extras] [Bug 443806] Dolphin should allow option to cache thumbnails for separate encrypted devices / locations

2023-05-14 Thread Payton Q
https://bugs.kde.org/show_bug.cgi?id=443806

--- Comment #30 from Payton Q  ---
Just a reminder that 411919 is not the same issue and that has already been
discussed. Please discuss on gitlab, not on that issue (or this one, but
especially not that one).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio-extras] [Bug 443806] Dolphin should allow option to cache thumbnails for separate encrypted devices / locations

2023-05-14 Thread Payton Q
https://bugs.kde.org/show_bug.cgi?id=443806

--- Comment #29 from Payton Q  ---
Just a reminder that 411919 is not the same issue and that has already been
discussed. Please discuss on gitlab, not on that issue (or this one, but
especially not that one).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio-extras] [Bug 443806] Dolphin should allow option to cache thumbnails for separate encrypted devices / locations

2023-05-13 Thread Payton Q
https://bugs.kde.org/show_bug.cgi?id=443806

--- Comment #25 from Payton Q  ---
Merge requests:

https://invent.kde.org/system/dolphin/-/merge_requests/548
https://invent.kde.org/frameworks/kio/-/merge_requests/1284

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio-extras] [Bug 443806] Dolphin should allow option to cache thumbnails for separate encrypted devices / locations

2023-05-13 Thread Payton Q
https://bugs.kde.org/show_bug.cgi?id=443806

Payton Q  changed:

   What|Removed |Added

  Alias||p
   Assignee|plasma-b...@kde.org |pmqui...@proton.me

-- 
You are receiving this mail because:
You are watching all bug changes.