Page MenuHomePhabricator

Invalid message lookup keys are rendered as double encoded HTML
Closed, ResolvedPublic

Description

Author: dee

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

  • <actionname-sectionname> --

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.


Version: 1.22.2
Severity: trivial

Details

Reference
bz62047

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 3:03 AM
bzimport set Reference to bz62047.
bzimport added a subscriber: Unknown Object (MLST).

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.

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