Page MenuHomePhabricator

Produce valid XHTML 2.0 output (when XHTML becomes a standard)
Closed, DeclinedPublic


Author: neubau

According to wikipedia, <a
2.0</a> will take another while to get drafted. XHTML will result in a major
break in terms of compatibility.

We won't have mainstream browser software for XHTML 2.0 in 2006 if everything
goes planned.

This feature request is a rather hard one: A lot of tags will be replaced from
our current output. Complying to XHTML 2.0 means rewriting almost every output
related part of the Mediawiki code, AFAIK.

This is the <a href="">future</a>....

Version: unspecified
Severity: enhancement



Revisions and Commits

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 21 2014, 8:41 PM
bzimport set Reference to bz2809.
bzimport added a subscriber: Unknown Object (MLST).

plugwash wrote:

from what i can gather xhtml 2 in its present form is basically unusable due to
the fact it doesn't allow pages to be authored in a backwards compatible manner.

if/when xhtml2 becomes useable this can possiblly be revisited but i see any
need/reason for mediawiki to be an early adoptor.

I'm gonna go wild and resolve this as LATER, which we haven't used much before. ;)

Generally speaking I don't think supporting XHTML 2.0 will be all that difficult --
mostly it should be a straightforward transformation of existing markup to new

Aside from the fact that there's no point in it until there's widespread browser support,
the main technical obstacle is that we still don't guarantee well-formed XML output to
begin with. Until the parser can guarantee proper nesting of elements, there would be
little point in expending the transformation effort either.

epriestley changed the task status from Declined to Resolved by committing Unknown Object (Diffusion Commit).Mar 4 2015, 8:15 AM
epriestley added a commit: Unknown Object (Diffusion Commit).
demon changed the task status from Resolved to Declined.Mar 4 2015, 8:36 AM
demon claimed this task.