Page MenuHomePhabricator

Navigable TOC: Wikitext in section titles not parsed
Closed, DeclinedPublic

Description

Author: wikibugs

Description:
Display in TOC when sections are defined with sub/super scripts

Reporting against Babaco Release. (Hosted on http://prototype.wikimedia.org)

Steps to Reproduce ::
1)Create a new page with various sections (levels)
2)Apply superscript/subscript to a part of sections' text
3)Check the display in table of content (please see the attachment)

<<Superscript/subscript syntax appear in table of content>>

Expected Outcome ::
Table of content shall not display the syntax.

Test Environment (Client) ::
Browser (User-Agent): Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2
Javascript: Enabled
Cookies Enabled: Enabled
Java Enabled: Enabled
CPU class/type: OS/CPU Windows NT 6.0
Screen Width x Height: 1280 x 800
Screen Color Depth: 32


Version: unspecified
Severity: minor
OS: Windows Vista
Platform: PC
URL: http://usability.wikimedia.org/wiki/Releases/Babaco/Compatibility_Matrix

Attached:

SectionWith-SubSuperScripts-2009-09-12.png (489×1 px, 29 KB)

Details

Reference
bz20602

Related Objects

View Standalone Graph
This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.
StatusSubtypeAssignedTask
ResolvedNone
DeclinedNone

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:47 PM
bzimport set Reference to bz20602.
bzimport added a subscriber: Unknown Object (MLST).

wikibugs wrote:

Added keyword babaco to the bug

WONTFIX? I don't think we can reliably tell what the header will be displayed as, so reflecting the wikicode version instead makes sense to me.

There are so many levels in which solving this sort of thing could fail, it's just not worth it at this point.

Another bug along these lines would be "headings created by templates are not shown".

The thing is, wikitext is horrible as it is, with very loose and sometimes inconsistent rules which are defined by a particular implementation of a parser which has yet to be successfully ported to another language without skipping over large functional areas.

So, in short, no, this will not be fixed until serious wikitext reform is achieved and a JavaScript wikitext parser is built.

Closing as WONTFIX as per comments 3 and 4.