Page MenuHomePhabricator

Visual editor creates wrong cite copies
Closed, InvalidPublic

Description

Hello. In the last time, VE creates wierd code during editing. If you make an edit in some page, you can get a code

[[<page name>#cite note-2|<span class="mw-reflink-text">[2]</span>]]

just after the "real" cite, sometimes multiple times. See, for example, this revision, and five references "2". And I see it in many pages. Thank you.

Related Objects

Event Timeline

Jdforrester-WMF changed the task status from Open to Stalled.May 30 2017, 7:11 PM
Jdforrester-WMF triaged this task as High priority.
Jdforrester-WMF moved this task from To Triage to TR0: Interrupt on the VisualEditor board.
Jdforrester-WMF subscribed.

Do you know if this is caused by users of a particular browser or browser extension? This kind of corruption is generally caused by those.

No, I don't. Do you want me to ask some? Bth, how the task can be high priority and stalled at the same time?

No, I don't. Do you want me to ask some?

Yes, please!

Bth, how the task can be high priority and stalled at the same time?

High priority to fix due to the severity of the problem (e.g. wikitext corruption), but presently unfixable pending more details on exactly what the problem is. :-)

In the past, this has been due exclusively to people copying the little blue clicky number from the "read" mode and pasting into the article the HTML that they actually copied – which, as it turns out, is <sup>[1]</sup> rather than <ref>{{cite web|url=www.example.com | title=Example Website}}</ref>.

Assuming that this is the same problem (and it looks like it to me), it's not a problem with VisualEditor (which did exactly what the user unintentionally asked it to do), and the underlying problem is not solvable until after we get Parsoid HTML everywhere.

No, I don't. Do you want me to ask some?

Yes, please!

Sorry for delay. Nobody answered, otherwise I would bring theirs answer immediatly here.

This bug report is not actionable without more details.

This bug report is not actionable without more details.

What details do you need. I can search for hundreds of diffs for you, but I think you need something else.

I think they need to know how to make this happen ("steps to reproduce").

I think they need to know how to make this happen ("steps to reproduce").

I'm not sure we can make it happen in purpose. It just happens all the time. But maybe I'm wrong. @Amire80?