The problem is due to an inefficient implementation of clip masks in the X-server. Clip masks are used to select the region of the display where the background is to show through. The problem has been observed on the following DEC X-servers:-
All X-windows versions of Netscape and Mosaic that support background images use clip masks when displaying a transparent image over a background image. Some versions of Netscape also use them (unnecessarily, I feel) with a solid (default or coloured) background: Unix Netscape 3.0 (initially beta 4) and VMS Netscape 2.02 (initially beta 1). This latter case is much more serious, since there are many many more web pages that could provoke it. I repeatedly reported the problem with Netscape 3.0b4, but have seen no response, fix, or acknowledgement from Netscape. Hopefully Netscape will incorporate DEC's fix (see below) in a future version of Unix Netscape.
The following implementations provide a workaround:-
Mosaic*MaxClipTransitions
, if
specified) transitions between background and foreground)
when it detects a DECWindows/VAX X-server.
A patch,
hopefully to be applied to future releases of both VAX and Unix Mosaic,
allows Mosaic*MaxClipTransitions
to be specified for
non-VAX X-servers, as well as automatically enabling it for VXT2000 and
eXcursion.
VMS-MOSAIC
mailing
list archives.
Do not select any of these links unless you are prepared to hang up your screen, perhaps for some time. If you want a safe example that shouldn't cause any problems have a look at this simple transparent image.
This page will display a more complex, but relatively small transparent image on the default background. Subsequent links allow you to try larger images (the problem gets dramatically worse as the image size increases) and background images. Alternatively, you can go to these pages directly using the following links, though with the danger of hanging your X-server even longer.
simple
,
small,
medium, and
large images.
simple
,
small,
medium, and
large images.