[kde] [Bug 493278] Can't copy embedded links in text by right click in QML software

[Nate Graham]

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

Nate Graham <nate at kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Product|plasmashell                 |kde
             Status|REPORTED                    |CONFIRMED
            Version|6.1.5                       |unspecified
                 CC|                            |nate at kde.org,
                   |                            |nicolas.fella at gmx.de
          Component|general                     |general
            Summary|KDE Plasma Settings can't   |Can't copy embedded links
                   |copy embedded links in text |in text by right click in
                   |by Right Click              |QML software
           Assignee|plasma-bugs at kde.org         |unassigned-bugs at kde.org
   Target Milestone|1.0                         |---
     Ever confirmed|0                           |1

--- Comment #1 from Nate Graham <nate at kde.org> ---
This is... complicated. In QML software there are multiple ways of making
clickable links within long text areas work, and to my knowledge none of them
implement what you're looking for.

This particular implementation in the user Feedback KCM is a QtQuick TextEdit
in read-only non-selectable mode. We could fairly easily implement the
requested feature right here, but that wouldn't help every other implementation
out there.

Options include:
- Actually implement it for every case (bad, obviously)
- Implement it for Kirigami.SelectableLabel and port everything to use that
(better, but sometimes selectability is overkill and giving something called
"SelectableLabel" a non-selectable mode is worthy of the mad hatter)
As above, but create a new non-selectable text component in Kirigami and port
non-selectable text labels to use it (maybe okay but at this point it's feeling
like we should just do it in Qt)
- Implement the feature in upstream QT components (harder, fewer people could
do it, would take like a year before we could actually use it anywhere)

What do you think would be the right place to fix this, Nicolas?

-- 
You are receiving this mail because:
You are the assignee for the bug.