Closed Bug 199418 Opened 21 years ago Closed 20 years ago

"hidden" images that appear with Ctrl-A under Internet Explorer don't work with Mozilla

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: bugzilla, Assigned: asa)

References

()

Details

this is really really important and serious bug...:)

going to
http://johnbanks.org/hit-ctrl-A.jpg
and hitting CTRL+A doesn't work as in Internet Explorer.
LOL okay that only works because microsoft is taking a short cut with blending a
blue colour on the image and even fails on IE as soon as it get scaled. Can
someone make this invalid or won't fix?

( oh check boarding that M$ does changes the picture from sun flowers to a porn
picture ).
*cough* Yes, anyone doing bug triage on this, don't attempt to reproduce in
IE... on the family computer... with parents in the room. =) My eyes glazed over
the word "porn" in comment #1.

Should we wontfix based upon comment #1?
This is a crude workaround, but it will render IE's ctrl-a equivalent in
Mozilla for this type of hidden image, and even has improved color fidelity
over IE.  (However it won't work in IE, which is 1 pixel off.)

<html><head></head><body background="http://johnbanks.org/hit-ctrl-A.jpg">
<img src="http://208.176.239.53/dts/mesh.png"></body></html>

Warning:  Before you copy and paste this into an HTML file, heed all
content warnings above.
Enough humor for now... sorry.
Product: Browser → Seamonkey
Okay, given that the URL is now 404 Not Found, let's put this bug out of its
misery.  If someone comes up with a new (preferably family friendly) testcase
and can make a legitimate case for emulating IEs behaviour, feel free to reopen!  ;)
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Summary: inverted image doesnt work → "hidden" images that appear with Ctrl-A under Internet Explorer don't work with Mozilla
I thought I put this bug out of its misery a LONG time ago ;-)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.