Last modified: 2012-04-12 13:56:14 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 27068 - Putting links in italic or bold text will eat up the space after the link.
Putting links in italic or bold text will eat up the space after the link.
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2011-01-31 13:34 UTC by Gergely Polonkai
Modified: 2012-04-12 13:56 UTC (History)
2 users (show)

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


Description Gergely Polonkai 2011-01-31 13:34:58 UTC
When I enter a longer text which is all italic (e.g a quote from a book), and put a link in it, the rendering engine eats the space following that link.


''When ''[[someone|''the emperor'']]'' sat on his throne''

This will be formatted italic for the whole sentence, but will look like this:

When the emperorsat on his throne
Comment 1 Platonides 2011-01-31 15:35:17 UTC
Can't reproduce on 1.16, 1.17 nor trunk.
Comment 2 Krinkle 2011-01-31 15:45:20 UTC
Test cases to show that this works in trunk and 1.16:

* trunk:
* 1.16:
Comment 3 Gergely Polonkai 2011-02-01 08:25:05 UTC
After a few hours of debugging it turned out to be an FCKeditor issue. Sorry for posting it here.
Comment 4 Platonides 2011-02-01 22:19:38 UTC
I'm happy you found out the issue.

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