4 ms·
Which way around is that? Firefox would be unable to use it's Clipboard and require restarting, or Wayland would require restarting. If it's the later, would i
by moritonal 5y ago
Which way around is that? Firefox would be unable to use it's Clipboard and require restarting, or Wayland would require restarting.
If it's the later, would it not imply a shaky foundation if an app is able to brick the systems compositor with something as simple as clipboard access?
- jborean93 5y agoAt least for me it would hang the app trying to retrieve the clipboard value that was set by Firefox. It would continue to hang until I either a) copied data from another app, or b) reloaded sway.
- boudin 5y agoIn Wayland the data of the clipboard stays in the app where it was "added" to the clipboard and only transit between the application where it was copied to the app where it is pasted when pasted. I think the issue was at this transit stage on Firefox side. It didn't have any impact on the compositor, it would behave differently in the receiving app. Some would crash, some would freeze for a bit, some would be totally fine but would just fail to get the data to paste.
- di4na 5y agoYep exactly this
- vidarh 5y ago> In Wayland the data of the clipboard stays in the app where it was "added" to the clipboard and only transit between the application where it was copied to the app where it is pasted when pasted. Back to the future... This was how the Amiga clipboard functionality worked (at that point it was because it saved memory), though you could push the data into separate clipboard storage if necessary (e.g. if an application was about to close while a clip was active, or because an application requested a paste).
- TingPing 5y agoIt's still a reasonable design, it even allows for passing around zero copy buffers, or streaming large data.