Page MenuHomePhabricator

VisualEditor: Numbering of references created inside templates/image captions re-uses existing numbers, doesn't continue
Closed, ResolvedPublic

Details

Reference
bz53486

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 1:59 AM
bzimport set Reference to bz53486.

<< Entering Visual Editor mode renumbered the references on page Python_(programming_language) https://en.wikipedia.org/wiki/Python_(programming_language)?veaction=edit , so they don't match the references listed at the end of the article. Davipo 08:36, 29 August 2013 (UTC) >>
It will ignore the numbers in the infobox, and start again from n.1 in the first line of the article - should be 11 instead. I find it just slightly confusing, since in the end you are still able to edit footnotes correctly. Thanks.

References in infobox not populating the main references list and not being counted sounds a lot like bug 51289 which was marked fixed at the start of the month

To clarify the first comment: if you look at the vedit view of the page I linked, you'll see that references 50 and 49 are both labelled "49". So, potentially we might be dealing with two distinct bugs here - renumbering because it's not factoring in different surfaces, and duplicate numbering.

Looking again, it seems this is not the same as the earlier bug. In that case the references from the infobox didn't appear in the reflist at all. Now it seems that it is just the numbering that is wrong. At [[Ptyhon (programming language)]] for example, there are 10 references in the infobox, so the first reference in the lead is numbered 11.

Looking at in VE though the first reference in the lead (TIOBE Software Index (2012)) is numbered 1. In the reference list though TIOBE Software Index (2012) is numbered as 11 and reference 1 is the first one from the infobox.

at en.wp user:KWW wonders if this is the same issue as bug 52300?

Actually, on review I'm pretty sure that this is a duplicate of bug 50474.

  • This bug has been marked as a duplicate of bug 50474 ***