Last modified: 2012-04-16 09:16:13 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 T29733, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 27733 - Sanitizer strips more underscores from id's in $wgExperimentalHtmlIds mode
Sanitizer strips more underscores from id's in $wgExperimentalHtmlIds mode
Status: NEW
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
unspecified
All All
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
http://test.wikipedia.org/wiki/User:D...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-02-26 02:55 UTC by Danny B.
Modified: 2012-04-16 09:16 UTC (History)
2 users (show)

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


Attachments

Description Danny B. 2011-02-26 02:55:06 UTC
When HTML5 is on, id's with more than one underscore in a row are converted the way one underscore remains only.

More underscores in a row is perfectly valid id, so absolutely no need to strip them.

This behavior breaks CSS and JS depending on such id's.
Comment 1 Bawolff (Brian Wolff) 2011-02-26 03:02:04 UTC
cc'ing Aryeh Gregor since (I believe) he did most of the $wgExperimentalHtmlIds stuff, he might know the rationale for stripping repeated underscores.
Comment 2 Aryeh Gregor (not reading bugmail, please e-mail directly) 2011-03-02 01:35:50 UTC
This is $wgExperimentalHtmlIds, not HTML5 per se.  I've disabled that by default in r83061 because of all these complaints.  Minimally, I could change it to not strip leading or trailing underscores and not collapse consecutive underscores; it seems like that would fix many of the complaints, at the expense of somewhat uglier id's.

What's some example CSS or JS that depends on such id's?  It's not really possible to evaluate a request like this without specific problem reports.

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


Navigation
Links