Last modified: 2009-08-13 18:37:55 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T22225, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 20225 - XHTML does not validate
XHTML does not validate
Status: RESOLVED DUPLICATE of bug 9530
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
http://en.wikipedia.org/wiki/Talk:Sof...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-13 18:25 UTC by Martin Leese
Modified: 2009-08-13 18:37 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Martin Leese 2009-08-13 18:25:39 UTC
Somebody on the Talk page given in the URL pointed out that the XHTML for that Talk page does not validate. I checked, and this is so. Here is the output from the validator:  

Validation Output:  1 Error
   1. Error Line 335, Column 45: value of attribute "id" invalid: "." cannot start a name
      <p><a name=".22Bug.22_defined_in_1892." id=".22Bug.22_defined_in_1892."></a></p>
      It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

The problem is caused by the following section heading:  
    "Bug" defined in 1892.

As you can see, each quotation mark is being converted to '.22' making the name/id attribute begin with a '.'.


Neat bug. One way to fix it would be to always add a leading dummy character to the attribute. This would make it look something like:  
    name="X.22Bug..."
Comment 1 Chad H. 2009-08-13 18:37:55 UTC

*** This bug has been marked as a duplicate of bug 9530 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links