Last modified: 2007-07-29 18:36:49 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 10742 - ProofreadPage slowly destroys HTML entities
ProofreadPage slowly destroys HTML entities
Product: MediaWiki extensions
Classification: Unclassified
ProofreadPage (Other open bugs)
All All
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-07-29 17:47 UTC by Graf.Zahl
Modified: 2007-07-29 18:36 UTC (History)
1 user (show)

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


Description Graf.Zahl 2007-07-29 17:47:58 UTC
To demonstrate the bug:

1. Open a page in the page namespace for which a page image exists (for example the URL given).

2. Enter something like  

3. Press "Show preview" repeatedly.

4. The string   will slowly be destroyed until only an ordinary space (not a non-breaking space) remains.

In real life, what typically happens is that a non-breaking space is converted to an ordinary space. This is very annoying. It does not happen on pages outside the page namespace.
Comment 1 ThomasV 2007-07-29 18:17:18 UTC
it might be due to the regexp matching in proofread.js
Comment 2 Graf.Zahl 2007-07-29 18:35:38 UTC
(In reply to comment #1)
> it might be due to the regexp matching in proofread.js

Maybe you could just replace all & with & before the splitting?
Comment 3 ThomasV 2007-07-29 18:36:49 UTC
fixed in svn

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