Closed Bug 228225 Opened 21 years ago Closed 19 years ago

Bad rendered link with images turned off

Categories

(Core :: Graphics: Image Blocking, defect)

x86
Windows 2000
defect
Not set
minor

Tracking

()

RESOLVED EXPIRED

People

(Reporter: asherman, Assigned: security-bugs)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031129
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031129

There is a link in this page:
http://shadow.telecet.ru:7500/content/index?p=page/enter&e[ok]=1&d[logintype]=own
that is not rendered with images turned off, so I cann't find it on this page.

Reproducible: Always

Steps to Reproduce:
1. Open http://www.telecet.ru with images being showed
2. Find the link
http://shadow.telecet.ru:7500/content/index?p=page/enter&e[ok]=1&d[logintype]=own
on the left side of the page
3. Turn images off
4. Reload this page
5. Try to find that link again.

Actual Results:  
The link
http://shadow.telecet.ru:7500/content/index?p=page/enter&e[ok]=1&d[logintype]=own
is not accessible with images turned off 

Expected Results:  
It should be accessible.
The image in question has alt="" this tells mozilla not to render any alt text
when it can't load the image.  Even if the page had alt set to something you
would run into bug 180620.
But It was earlier If a image was a link that was rendered just as a box because
link is important element to render!
So should It be marked as dup. of  bug 180620?
Ahh, I think I see what you want.  You would like an outline of where the image
would have been if you where loading images.  That would be Bug 98554.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.