Closed Bug 440516 Opened 16 years ago Closed 16 years ago

URL in the statusbar when cursor is on image points to URL of current phpBB forum topic

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
minor

Tracking

()

RESOLVED INVALID

People

(Reporter: ivekpro, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008052912 Firefox/3.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008052912 Firefox/3.0

First of all, please don't mind the picture that describes it.
When i browse some forums, with pictures that are uploaded to imageshack for example, my statusbar reads the URL of the current topic, instead of the URL of that image ( e.g: forum.mozilla.org/viewtopic.php?t=1111 is being displayed instead of http://img291.imageshack.us/img291/image.jpg ).

When I move the cursor away from the image, then put it back on, the image URL is being displayed correctly as it should.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
I just wanted to add that the cursor was on the picture in the moment of screenshot taking, only my program missed it.

Sorry for my English, i'm from Serbia.
The statusbar shows that because that's where the link goes: the HTML in the post is (abbreviated somewhat) "<a href="http://imageshack.us"><a href=""><img src="http://imageshack.us/pic.jpg"></a></a>" and since links absolutely cannot be nested like that, Firefox treats it as <a href="imageshack"></a><a href=""><img></a>, and so the image is linked to "", which is the URL of the page where you are.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Also noticed that with tinypic.com and some other image hosting websites. Don't know is that a Firefox bug or choppy thumbnail code, but version 2.0.0.14 haven't had problem with that.
I also checked with several other phpBB forums, and it's always the same.
My appologies to all. It was choppy image resizing code that few of those forums use. Aparently, it's no bug.
You need to log in before you can comment on or make changes to this bug.