Page MenuHomePhabricator

Flow: title editing exceptions: htmlParseStartTag, and htmlParseEntityRef
Closed, ResolvedPublic



Jay8g reports:

"&" in the topic title gives "The error message received was: Exception Caught: htmlParseEntityRef: no name" and refuse to post.

"<" or "<>" in the topic title (but not ">", "</>" or "<[anything]>", which post) give "The error message received was: Exception Caught: htmlParseStartTag: invalid element name" and refuse to post.

See screenshot for confirmation of the first.

Version: unspecified
Severity: normal
See Also:




Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 3:10 AM
bzimport set Reference to bz65570.
bzimport added a subscriber: Unknown Object (MLST).
Quiddity created this task.May 21 2014, 1:21 AM

The PHP exception happens in Parsoid/ReferenceExtractor.php's extractReferences() when it calls createDOM() to record references in the new version of the TopicListBlock. I guess the title content isn't escaped correctly. But Flow should probably not even attempt to record references for title text since nothing in a title is parsed!

To summarize titles in Fl, HTML tags in titles

  • Can cause the exception in this bug.
  • Incorrectly take effect while previewing (e.g. <em> and <br> cause italics and line breaks).
  • Turn into &amp; &lt; &gt; pairs when you edit them (bug 65143).

I think we want a Flow topic title to be an unparsed escaped string, so whatever you enter in it is shown "as is" and has no effect. Limited parsing of titles is an enhancement request.

  • Bug 65759 has been marked as a duplicate of this bug. ***

Change 136270 had a related patch set uploaded by Bsitu:
Should not try to parse reference from topic title

Change 136270 merged by jenkins-bot:
Should not try to parse reference from topic title

Quiddity removed a subscriber: Maryana.Dec 19 2014, 1:36 AM