https://bugs.kde.org/show_bug.cgi?id=476714
`{third: "Beedell", first: "Roke"}`{.JSON5}
<rvdois+rvu...@rokejulianlockhart.anonaddy.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #2 from `{third: "Beedell", first: "Roke"}`{.JSON5}
<rvdois+rvu...@rokejulianlockhart.anonaddy.com> ---
(In reply to Noah Davis from comment #1)
> I'm having trouble understanding this report. Are there two issues here? If
> so, there should be 2 separate reports. Are any of these issues duplicates
> of https://bugs.kde.org/show_bug.cgi?id=447831 or
> https://bugs.kde.org/show_bug.cgi?id=465781?
>
> Copy should only ever have one format at the moment, so I'm a bit confused
> about why you say Save As changes the behavior. The format should be the raw
> data of the image with the "application/x-qt-image" mimetype. See
> https://bugs.kde.org/show_bug.cgi?id=465781#c8 for a more detailed
> explanation if you're curious.
It *could* be considered a duplicate of
https://bugs.kde.org/show_bug.cgi?id=447831 per
https://bugs.kde.org/show_bug.cgi?id=447831#c0 (its description) but the title
of that issue is unnecessarily specific – I'd much prefer that it be considered
a duplicate of this considering that my description is a lot more specific
about exactly the issue that causes this, and thus why I want this. It's not a
duplicate of the other because this requires "Save as" to cause what that
describes.
I don't believe that this is two issues in one because I find that the "Save
as" issue of sorts actually acts as a great workaround for now, since without
it, there would be no (obvious?) way to save a screenshot as anything except
the default MIME type.
--
You are receiving this mail because:
You are watching all bug changes.
