onmousedown and access denied problem after applying KB824145

[Walter]

We have an app that uses local only HTML pages (all pages
exist on the client's machine) to display some data. This
pages have some IFRAMES embedded in them. On one page, we
capture the onmousedown event and in that event we call
some JavaScript that will eventually call resizeTo for
another IFRAME. After applying patch KB82414, this process
caused resizeTo to throw an "Access Denied" error. After
this error is thrown, any attempt to resize an IFrame from
another frame (even if the IFrame calls a function in the
other IFrame that internally call resizeTo on itself) will
cause this error to occur.

The strange thing is that if we instead use any other
mouse event, like onmouseup, onmouseover and onmouseout
the problem does not occur. It's only the onmousedown
event that has this problem.

We were able to get around the problem by switching from
onmousedown to onmouseup, but we were wondering if anyone
else is having this problem and if Microsoft is aware of
the problem.

 

[R Shoemaker]

We were able to get around the problem by switching from
onmousedown to onmouseup, but we were wondering if anyone
else is having this problem and if Microsoft is aware of
the problem.

Indeed, I encountered this today. My situation is almost identical.

I have an onmousedown event which navigates to a different URL. The
navigation causes a call to ResizeTo() on page load. If the page is
accessed through a bookmark, everything is fine. If the page is loaded
as a result of the onmousedown event, I get Access Denied.

My only resolution right now is to work around it with a different event
sequence. I am hoping MS addresses this before I have to modify
deployed applications.