Last modified: 2005-07-23 05:34:32 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 T3247, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 1247 - charinsert not properly working with IE 6.0
charinsert not properly working with IE 6.0
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
PC All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 1309 1465 (view as bug list)
Depends on:
Blocks: javascript 640
  Show dependency treegraph
 
Reported: 2005-01-02 00:20 UTC by Alfio Puglisi
Modified: 2005-07-23 05:34 UTC (History)
3 users (show)

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


Attachments

Description Alfio Puglisi 2005-01-02 00:20:55 UTC
Using IE 6.0 on windows 2000 the charinsert extension doesn't work. Encoding
seems correct: UTF-8, left to right. Clicking on these characters one time each:

È à é è ì í ó ò ù ä ë ï ö ü ~

has the following result:

Ãà éèìíóòùäëïöü~

With Firefox 1.0 the extension works correctly. Tested on en: and it:
Comment 1 Brion Vibber 2005-01-07 03:34:19 UTC
Possibly triggered by the URL-escaping. The actual extension doesn't do this, though; it might be another tidy abomination mucking 
with the HTML output.
Comment 2 Zigger 2005-01-11 02:37:51 UTC
*** Bug 1309 has been marked as a duplicate of this bug. ***
Comment 3 Zigger 2005-01-11 02:40:58 UTC
Duplicate bug 1309 was for site http://ang.wikipedia.org
Comment 4 Brion Vibber 2005-02-05 01:31:01 UTC
*** Bug 1465 has been marked as a duplicate of this bug. ***
Comment 5 Brion Vibber 2005-02-05 01:33:55 UTC
Adding these options to the tidy config fixes it:
  fix-backslash: no
  fix-uri: no

When on these don't fix actual HTML validation issues, but do corrupt javascript: URLs and possibly other things.

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


Navigation
Links