Last modified: 2014-04-21 21:42:25 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 T66162, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 64162 - /reF tag was changed to /ref even though user did not intend it
/reF tag was changed to /ref even though user did not intend it
Status: RESOLVED DUPLICATE of bug 55461
Product: Parsoid
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Gabriel Wicke
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-20 19:11 UTC by Alex Monk
Modified: 2014-04-21 21:42 UTC (History)
3 users (show)

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


Attachments

Description Alex Monk 2014-04-20 19:11:31 UTC
See https://office.wikimedia.org/?diff=110032 for an example (private, sorry)

This -might- be a VE issue, not sure
Comment 1 Roan Kattouw 2014-04-20 21:06:16 UTC
Note that the opening tag was <ref> but the closing tag was </reF>. I didn't know you could do that in wikitext.
Comment 2 Roan Kattouw 2014-04-21 21:16:51 UTC
I now can't reproduce while editing that oldid :( nor with a <ref>...</reF> example on my local wiki.
Comment 3 ssastry 2014-04-21 21:20:33 UTC
Roan: this looks like a transient dom diff (either because of the cached version was not available for the diff which lead Parsoid to reparse which could have generated different ref ids causing that ref to get marked edited) which could then forced a full serialization of that ref.
Comment 4 Alex Monk 2014-04-21 21:35:21 UTC
It *might* be that I accidentally touched that reference and undid/cancelled. Or something.
Comment 5 ssastry 2014-04-21 21:42:25 UTC

*** This bug has been marked as a duplicate of bug 55461 ***

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


Navigation
Links