Last modified: 2008-04-07 21:40: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 13621 - Diff display sometimes does not hightlight the entire change
Diff display sometimes does not hightlight the entire change
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
PC Windows Vista
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2008-04-06 04:20 UTC by Tom N
Modified: 2008-04-07 21:40 UTC (History)
0 users

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


Description Tom N 2008-04-06 04:20:12 UTC

The old text contained: [[Led Zeppelin]], [[Black Sabbath]]
The new text contained: [[Led Zeppelin]], [[King Crimson]], [[Black Sabbath]]

The highlighted difference was expected to be "[[King Crimson]], " or "]], [[King Crimson" or something similar.  However, only the "]]" following "Led Zeppelin" was highlighted.
Comment 1 Tom N 2008-04-06 04:35:00 UTC
I've examined the HTML page source and found the text:

 [[Led Zeppelin<span class="diffchange">]], [[King Crimson</span>]], [[Black Sabbath]]

This appears to be correct.  And I have now found that the page displays correctly in IE.  This this appears to be a Firefox bug.
(Firefox version string: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv: Gecko/20080311 Firefox/
Comment 2 Brion Vibber 2008-04-07 21:40:14 UTC
Looks just fine in Firefox 3.0b5.

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