"Put link in clipboard" does not work with Linux
Frank Steiner - April 15, 2008 - 14:20
| Project: | Web File Manager |
| Version: | 6.x-2.9-alpha2 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | patch (reviewed & tested by the community) |
Description
Hi,
the "put link in clipboard" would be a great feature to create anchors in the body editor! Unfortunately it doesn't work with Linux (tested with Firefox). The Javascript console shows
clip:<a href ...
but I cannot paste the link, neither with Ctrl-V nor with the middle mouse button (which is the standard clipboard in Unix).
I can't test if it works in Windows, so I'm not sure if the feature just doesn't work in the 6.x release or just not in Linux. In the latter case I hope it can be made linux-compatible, because this feature really is nice!
cu,
Frank
#1
I had to learn that Opera just does not support this :-( and for Firefox you have to allow this explicitely. Therefore I've written to small patches: One to alert Firefox users when and how they must enable copying to clipboard.
The other one warns Opera users that the clipboard is not supported but to give them a similar functionality, the patch replaces the address of file nodes by their link. I.e., I changed
this.clickObj.setAttribute('href', '#' );to
this.clickObj.setAttribute('href', getBaseUrl() + "\/webfm_send\/" + fileObj.id );if the browser is Opera and the file is in the database. Thus, Opera users can right-click on the file name in either the attachment list or the filetree (since they don't get the webfm context menu, see http://drupal.org/node/246918) and copy the files adress to the clipboard by Opera "Copy link address".
I'm not sure if you like that because I don't know if changing the file nodes address changes something else. Drag&drop etc. all still seemed to work, but you will know better :-)
If this patch doesn't destroy anything else, maybe it could be used as clipboard replacement for Opera users.
#2
Sorry, double post :-)
#3
OK and OK. next post...
#4
fixed in 5 branch only at this time
#5
Just opening this up for the 6.x version so that it doesn't get missed.
I'm going to make a broader release that merges 5.x changes into 6.x to bring it up to 2.13 soon.
andre