Last modified: 2007-04-17 17:40:50 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 7955 - '<' and '>' in attributes doubly encoded in queries
'<' and '>' in attributes doubly encoded in queries
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-11-16 20:24 UTC by Thomas Bleher
Modified: 2007-04-17 17:40 UTC (History)
0 users

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


Description Thomas Bleher 2006-11-16 20:24:50 UTC
When querying an attribute which contains a '<' or '>', these chars are doubly encoded, so the user 
sees &lt; (or &gt;). You can see it for example on, right at the bottom of the page.
Comment 1 Markus Krötzsch 2007-02-13 17:32:17 UTC
I think this bug is an instance of a general problem: SMW escapes all "&" in a
string. In cases where they belong to an HTML escape, this is not correct. The
assumption here is that we want to store the text as printed, not as typed, i.e.
we want "&" and "&amp;" to be stored as the same thing. So SMW would need to
check whether or not some & is part of a (supported) HTML escape. Maybe we can
just use some of PHP's HTML escaping to prevent this from happening.
Comment 2 Markus Krötzsch 2007-04-17 17:40:50 UTC
The encoding now has been fixed using MW's Sanitizer.

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