disabling 'refresh alert' in ie

[Chamomile]

Does anyone know a way to disable the 'refresh alert' windown that pops up
in ie
when document.location.reload() is used on a page that has post data?

In thecontext I'm using reload() this message is definitely not required
and tends to worry the user.
In fact it makes no difference whether the user chooses 'Retry' or 'Cancel'
,
but simply being presented with an official looking pop-up and what looks
like an important decision
is off-putting.

Firefox doesn't seem to feel the need to fire this alert.

[Chamomile]

If you have the data from the submitted form, may be you can do that as a

submit

with hidden input fields, instead of a reload. That way the data gets

submitted

like a regular form.

Tom
--

Thanks, but I'm not sure what you mean. The reload() was only really a work
around
for hiding a lot of select boxes that refuse to go away when a container's
visibility is set to 'hidden'.
(its a well known 'feature' of ie) - that is, a reload or refresh of the
page gets rid of the mess created when the
containers are set to 'hidden' leaving a random collection of ghost select
boxes. I was trying to find a
simple way to automatically 'clean up' the page - without asking the user to
hit 'refresh' - unfortunately I just
moved the problem to a different place. Instead of the user being presented
with an ugly mess of half hidden select boxes
they get a puzzling request alert which on balance is only slightly
better...

[VK]

Chamomile wrote:

Thanks, but I'm not sure what you mean. The reload() was only really a work
around
for hiding a lot of select boxes that refuse to go away when a container's
visibility is set to 'hidden'.
(its a well known 'feature' of ie)

With my 10 years experience I failed to meet such IE feature yet. I'm
well aware of "super z" (a.k.a. "firing through") effect for form
controls on IE before IE7 but it doesn't sound like what you are
describing. Can you port a sample for a publicly accessible link? What
IE version are you working with?

that is, a reload or refresh of the
page gets rid of the mess created

With form method="POST" (and this is what you have) hitting Reload
means "resubmit form to get the response formed the current page".
Respectively navigating back means "get me the page resulted from
submitting that form". So besides confusing visitors you are creating
needless load on your server. Both actions and warnings for them are
regulated by special settings in Tools Internet Options so they are
out of your runtime control.

You may change form method to GET, but IMO as a page layout failure the
problem should be cured by correcting the layout, not by twisting the
transaction process.

Again - a link would be most helpful.