92244 - ctrl-click on 1st image in View Page Info breaks further image viewing

Status: VERIFIED DUPLICATE of bug 101610

(SeaMonkey :: Page Info, defect)

Description

[GavinS]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.2+) Gecko/20010724
BuildID:    20010724

When using the 'View Page Info->Images tab, with multiple images, if you hold
the CONTROL key when clicking the left mouse button to view THE FIRST image,
then the image viewing is broken, and you can't change the selection again to
any other images.

Using CTRL-LMB on any image apart from the first one does not cause this breakage.

Going to another tab and back again does not fix things.

Closing the Page Info Dialog, and re-opening it DOES fix this.

I'm not sure if CTRL-LMB is supposed to do anything special, but it should be
just ignored if it is not doing anything special, and not cause the image
viewing to break.


Reproducible: Always
Steps to Reproduce:
1. Go to a page containing multiple images
2. Go to 'View Page Info->Images' tab
3. Hold Ctrl and click on the FIRST item in the list.
4. After releasing CTRL, then you can't select any more images.

Actual Results:  Viewing any more images is broken

Expected Results:  Should be able to carry on viewing images as normal

Comment 1

[GavinS]

Add a 2.5 into the Steps to Reproduce:

2.5) Select an image other than the first from the list of images.

Comment 2

[Jesse Ruderman]

I see this on WinNT, too, but it happens no matter which image I ctrl-click on.

Comment 3

[Daniel Brooks [:db48x]]

Yes, I basically see the same thing. I think I know why it's happening, but by
any chance do you see javascript errors at any point while reproducing the bug?

thanks

Comment 4

[GavinS]

I get nothing in the terminal, and the following when opening up the Page Info,
and that is all...

>> Warning: reference to undefined property window.arguments[1]
>> Source File: chrome://navigator/content/pageInfo.js
>> Line: 75

Comment 5

[Blake Ross]

-> Jesse

Comment 6

[Jesse Ruderman]

*** This bug has been marked as a duplicate of 101610 ***

Comment 7

[sairuh (rarely reading bugmail)]

mass verification of duplicate bugs: to find all bugspam pertaining to this, set
your search string to "DuplicateBugsBelongInZahadum".

if you think this particular bug is *not* a duplicate, please provide a
compelling reason, as well as check a recent *trunk* build (on the appropriate
platform[s]), before reopening.