Discussion:
IE 6 fails to render SELECT tag when body has gradient filter and user scrolls
(too old to reply)
Mark Schneider
2003-12-18 16:08:46 UTC
Permalink
Apparently, if you use Microsoft's gradient filter in a
style definition for the BODY tag and you have a form
with a SELECT tag (DropDownList in the case of aspx) and
the page is scrollable, IE will fail to render the SELECT
tag when the user scrolls up and down the page. To see:

<html>

<head>
<style>
BODY {
filter:progid:DXImageTransform.Microsoft.Gradient
(GradientType=0, StartColorStr='#00000000',
EndColorStr='#90000060') }
</style>
</head>

<body>

<p style="padding-bottom: 300px;">Top of page</p>

<center>
<form name="Form2" method="post" action="Webform1.aspx"
id="Form2">

<p>Scroll page and watch SELECT tag disappear!</p>

<select><option>Test</option></select>

<p>Scroll page and watch SELECT tag disappear!</p>

</form>
</center>

<p style="padding-top: 1200px;">Bottom of page</p>

</body>

</html>


Does anyone know if this is an acknowledged defect and if
so, whether a fix is in the works?

Thanks,
Mark Schneider
SOE Software Corporation


[My appologies in advance to most people out there
reading the microsoft.public newsgroups if this group
doesn't seem like the most one for my particular
question. For MSDN Subscribers to get a guaranteed reply
from Microsoft, we must use Microsoft's "managed
newsgroups", which contains a mere subset of all
microsoft.public groups - and of that subset, this groups
seems to be the most appropriate.]
Eldon Lei [MSFT]
2003-12-23 23:25:17 UTC
Permalink
Hi Mark:

We really appreciate your patience in getting a response from us. Using
your code we can reproduce the problem 100% of the time. Further more, the
problem does not show up if a textbox or a button is used on the page.
There is a special characteristic for the <select> element. It is the only
HTML element that is windowed. Meaning that it contains a window object
itself and process messages. This behavior looks like a bug to me, and in
my brief research this does not appear to be a known problem.

What I would recommend is to open a support incident with Microsoft
Developer Support. Since this is a bug, the incident will be refunded so
you will not be charged. They can investigate into it and explore
workarounds that could fit your needs.

Hope this helps,
Eldon Lei

Loading...