Last modified: 2013-09-20 06:00:31 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 T54446, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 52446 - VisualEditor: Copying and pasting the first reference on a page, then deleting the pasted reference results in ref "0"
VisualEditor: Copying and pasting the first reference on a page, then deletin...
Status: RESOLVED FIXED
Product: VisualEditor
Classification: Unclassified
Data Model (Other open bugs)
unspecified
All All
: Normal normal
: VE-deploy-2013-09-05
Assigned To: Ed Sanders
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-02 08:44 UTC by Mr. Stradivarius
Modified: 2013-09-20 06:00 UTC (History)
5 users (show)

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


Attachments

Description Mr. Stradivarius 2013-08-02 08:44:18 UTC
I was able to produce a reference labelled "0" in the VisualEditor using the following steps:

1. Create a simple page with some text and a reference. (I've made an example at [[User:Mr. Stradivarius/ref0]].)
2. Copy and paste the reference to somewhere else in the page.
3. Delete the reference from the text that has just been copied and pasted.
4. The first reference is automatically renumbered to "0".

The numbering of the first is fixed (back to "1") if you delete the line of text that you were on, but if you add new lines of text the first reference remains laballed "0" even if the pasted line is subsequently removed. The numbering still starts at 0 if you add another reference, so you get ref "0", ref "1", etc.

This is on Firefox 22.
Comment 1 Mr. Stradivarius 2013-08-02 08:45:27 UTC
Also, this is just in the editing window. When the page is saved, the numbering returns to normal.
Comment 2 James Forrester 2013-09-20 06:00:31 UTC
Confirming that this bug is now fixed, almost certainly in the re-write of copy-and-paste for nodes that happened for the 5 September release. Apologies for the slow triage at my end.

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


Navigation
Links