Last modified: 2013-06-21 02:37:26 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 T51536, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 49536 - VisualEditor: Incorrectly handling nested reference tags (blocked by Parsoid)
VisualEditor: Incorrectly handling nested reference tags (blocked by Parsoid)
Status: RESOLVED FIXED
Product: VisualEditor
Classification: Unclassified
Editing Tools (Other open bugs)
unspecified
All All
: High normal
: VE-deploy-2013-06-20
Assigned To: Trevor Parscal
:
Depends on: 49555
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-13 17:09 UTC by Oliver Keyes
Modified: 2013-06-21 02:37 UTC (History)
3 users (show)

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


Attachments

Description Oliver Keyes 2013-06-13 17:09:46 UTC
This is a particular problem with 'note' sections, and references used as notes; they commonly include citations for their statements, and you end up with markup that looks like <ref> some text here <ref> a citation for that text</ref></ref>

The VE is for some reason displaying it as a citation template, "some text here", a second citation template and a random </ref> tag. See note 1 in https://en.wikipedia.org/wiki/Fomitiporia_ellipsoidea for example.
Comment 1 James Forrester 2013-06-14 00:07:41 UTC
This is because Parsoid doesn't support the "#tag:ref" hack to let you do multi-level references (which were explicitly not allowed because of the insanity this creates :-)).

Creating a secondary bug (VE currently assumes you can't have nested references, which is indeed what Parsoid gives us), bug 49555. Once Parsoid supports this, we'll need to check that we correctly handle this from a UX perspective (amongst other things).
Comment 2 James Forrester 2013-06-21 02:37:26 UTC
This is now "fixed" (but we may want to make it a nicer experience in the future).

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


Navigation
Links