Page MenuHomePhabricator

[Google toolbar] IP users browsing to a non-existent page produces partial output in IE8/9
Closed, DeclinedPublic

Description

Author: peterrh

Description:
If an IP user browses to a non-existent page they get partial output. This happens on both Monobook and Vector skins. I haven't tested the others but my guess is it happens on all skins.

To reproduce, make sure you are not logged in to Wikipedia and browse to http://en.wikipedia.org/wiki/Ajadfhlkhlkh. The HTML you get begins:

s" title="How to contact Wikipedia">Contact Wikipedia</a></li>

		</ul>

</div>
</div>

<!-- /interaction -->

It then continues normally to the </html> tag. I am seeing the same thing on my site using 1.20.0 - www.festipedia.org.uk.

If you add ?useskin=monobook to the url the output is a little different but the same basic problem exists - the browser only receives the last portion of the HTML for the page.

This defect was also present in 1.19.x so this may be a duplicate. However, if it has been raised before I am surprised it hasn't been fixed. It gives a poor experience to IP users.


Version: 1.20.x
Severity: major

Details

Reference
bz42408

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 12:55 AM
bzimport set Reference to bz42408.
bzimport added a subscriber: Unknown Object (MLST).

Works for me. I can't find anything weird in the HTML.

peterrh wrote:

Thank you. That prompted me to look again.

It works correctly in Chrome and Firefox and IE6 (using a virtual XP machine) but I am seeing the problem on IE8 on Windows XP and IE9 on Windows 7 on several different PCs. Toggling Compatibility View makes no difference. Strange. I have updated the defect to note that only IE is affected.

mediawiki wrote:

Works for me on IE8 on Windows XP and IE8+IE9 on Windows 7

Valerie.m.juarez wrote:

This also works for me on Windows Vista IE 9 and in Compatibility View.

Three people could not reproduce the problem, so I'm marking this as RESOLVED WORKSFORME.

peterrh wrote:

(In reply to comment #5)

Three people could not reproduce the problem, so I'm marking this as RESOLVED
WORKSFORME.

On further investigation I've discovered that this is an interaction between IE and the Google toolbar which causes custom 404 error pages to be mishandled. If you turn off the "Provide suggestions on navigation errors" option in the Google toolbar (or don't have the Google toolbar in the first place!) everything is fine. One for Google to fix methinks.