Page MenuHomePhabricator

When viewing a talk page history, when NOT logged in, different results are shown in internet explorer, compared to firefox
Closed, ResolvedPublic

Description

Author: chzz

Description:
When not logged in,

http://en.wikipedia.org/w/index.php?title=Talk:Dominique_Strauss-Kahn_sexual_assault_case&action=history

As of now,

In Firefox v 4.0.1, the first entry is,
15:47, 31 May 2011
(Which is correct; the most recent entry)

In Explorer 9.0.8112, the first entry is,
02:59, 26 May 2011
(It does not show entries newer than that)

If logged in, both show the same (most recent) revisions.

The actual HTML code ('view source') seems to differ.

Adding a limit seems to 'solve' it, ie the following looks the same on both (showing the most recent entry);

http://en.wikipedia.org/w/index.php?title=Talk:Dominique_Strauss-Kahn_sexual_assault_case&limit=50&action=history


Version: unspecified
Severity: normal

Details

Reference
bz29220

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 21 2014, 11:35 PM
bzimport set Reference to bz29220.
bzimport added a subscriber: Unknown Object (MLST).

chzz wrote:

(In reply to comment #0)

When not logged in,

http://en.wikipedia.org/w/index.php?title=Talk:Dominique_Strauss-Kahn_sexual_assault_case&action=history

As of now,

In Firefox v 4.0.1, the first entry is,
15:47, 31 May 2011
(Which is correct; the most recent entry)

In Explorer 9.0.8112, the first entry is,
02:59, 26 May 2011
(It does not show entries newer than that)

If logged in, both show the same (most recent) revisions.

The actual HTML code ('view source') seems to differ.

Adding a limit seems to 'solve' it, ie the following looks the same on both
(showing the most recent entry);

http://en.wikipedia.org/w/index.php?title=Talk:Dominique_Strauss-Kahn_sexual_assault_case&limit=50&action=history

-This problem was reported on the help desk;

http://en.wikipedia.org/wiki/Wikipedia:Help_desk#RC_in_one_category_but_not_another_one

So PLEASE ALSO REPLY THERE with any update. Thanks

Reopening... I don't see why it was marked as fixed.

When closing the bug, please make sure you include the *reason* you
are closing it.