Last modified: 2009-08-02 22:26:23 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 T22043, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 20043 - Automatic anchor generated for duplicate header names can conflict with anchor for header with the same name
Automatic anchor generated for duplicate header names can conflict with ancho...
Status: RESOLVED DUPLICATE of bug 10025
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
unspecified
All All
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-02 22:20 UTC by SoWhy
Modified: 2009-08-02 22:26 UTC (History)
1 user (show)

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


Attachments

Description SoWhy 2009-08-02 22:20:25 UTC
It's not really important but should be changed/fixed anyway: 
If one uses the same header name multiple times (which can happen on talk pages quite often), the MW software will call the anchors for the second, third, etc. header "XXX 2", "XXX 3", etc. But if there exists both two headers called "XXX" and one called "XXX 2", the software will generate the anchor "XXX 2" twice - once for the duplicate header and once for the one that really is named that way. See this example here: http://en.wikipedia.org/wiki/User:SoWhy/sandbox (the second and third item in the TOC have the same anchor). 
As such, the software needs to be changed to check for duplicated anchors or find an unique way to handle such duplicated headers. 

Regards
SoWhy
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2009-08-02 22:26:23 UTC

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

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


Navigation
Links