Last modified: 2013-02-25 23:14:27 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T40033, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 38033 - VisualEditor: Cut-n-paste to external sources gives broken links as URIs point to # not their destination
VisualEditor: Cut-n-paste to external sources gives broken links as URIs poin...
Status: RESOLVED FIXED
Product: VisualEditor
Classification: Unclassified
ContentEditable (Other open bugs)
unspecified
All All
: High normal
: VE-deploy-2013-02-18
Assigned To: Inez Korczyński
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-28 17:40 UTC by Brion Vibber
Modified: 2013-02-25 23:14 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Brion Vibber 2012-06-28 17:40:05 UTC
When copy-pasting from the VisualEditor into LibreOffice 3 (tested 3.5.2.2 on Ubuntu 12.04), links are copied with the target URL of the wiki page being edited plus "#" on the end, eg <https://www.mediawiki.org/wiki/VisualEditor:Welcome#>

This doesn't happen when copy-pasting from the view mode.

See also bug 33239 comment 6 -- if we retain the original href and use JavaScript to suppress regular clicking, I think this would lead to more natural cut-n-paste behavior with other apps.
Comment 1 James Forrester 2012-06-29 00:42:03 UTC
Add see-also to bug 33105 which wants rich copy-and-paste - this is distinct but related.
Comment 2 Roan Kattouw 2012-11-11 01:25:20 UTC
This is a bit better now, but not quite there yet. External links now point to the correct destination, but internal links don't, they just contain the name of the page in the href.
Comment 3 James Forrester 2013-02-25 23:14:27 UTC
This is now fully correct; closing as fixed.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links