Last modified: 2014-06-07 08:42:14 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 T64047, the corresponding Phabricator task for complete and up-to-date bug report information.

Bug 62047 - Invalid message lookup keys are rendered as double encoded HTML


Summary:	Invalid message lookup keys are rendered as double encoded HTML

Status:	RESOLVED DUPLICATE of bug 66199

Product:	MediaWiki
Classification:	Unclassified
Component:	HTMLForm (Other open bugs)
Version:	1.22.2
Hardware:	All All

Importance:	Low trivial (vote)
Target Milestone:	---
Assigned To:	Nobody - You can work on this!

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-02-28 11:51 UTC by Deanna Earley
Modified:	2014-06-07 08:42 UTC (History)
CC List:	1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Deanna Earley 2014-02-28 11:51:50 UTC

Seen when reporting Bug 62046, the section names are double HTML entity encoded when then lookup key is not found.

    -- &lt;actionname-sectionname&gt; --

If the message is found but contains < and >, they are correctly encoded just the once.

All other missing messages render as:
  <messagename>

Seen on both 1.21.5 and 1.22.2.

Comment 1 Bawolff (Brian Wolff) 2014-02-28 11:56:33 UTC

This is true in quite a few places.

Generally its assumed that message keys are never missing, so if its missing its always a bug, thus not really a big deal if the missing message code is double escaped in some places.

Comment 2 Krinkle 2014-06-07 08:42:14 UTC


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

Wikimedia Bugzilla is closed!

Search

Personal tools

Navigation

Links