Page MenuHomePhabricator

Hovercards loses manual superscript formatting by requesting plain text
Closed, DuplicatePublic


The articles w:en:Googol and w:en:Googolplex include a <sup>foo</sup> string, which is not correctly displayed in Hovercards.

Screenshot from 2015-09-10 11:01:40.png (783×1 px, 177 KB)

Screenshot from 2015-09-10 11:01:21.png (783×1 px, 195 KB)

Related Objects

Event Timeline

Quiddity raised the priority of this task from to Needs Triage.
Quiddity updated the task description. (Show Details)
Quiddity subscribed.
Jdlrobson renamed this task from Add support for manual superscript formatting to Hovercards or TextExtracts to Hovercards loses manual superscript formatting by requesting plain text.Sep 18 2015, 8:23 PM
Jdlrobson triaged this task as Medium priority.
Jdlrobson removed a project: TextExtracts.
Jdlrobson set Security to None.

… Hovercards should probably request HTML.

What would be the implications of doing this? Are there elements known to be in the initial excerpt that are sure to mess up the Hovercard?

Potentially. We'd need to explore it. I'd expect that we'd need to parse the output into a DOM tree and whitelist only a few images e.g. p tags, sub, and sup.

I'd suggest to implement this we'd try a different mode e.g. explainhtmlsubset and test out on mobile first.

dr0ptp4kt lowered the priority of this task from Medium to Low.Aug 4 2016, 3:35 PM
dr0ptp4kt moved this task from Incoming to Triaged but Future on the Web-Team-Backlog board.

Related to (loading plain text instead of HTML):

should we track tasks like this under one task?