Two Gripes about IE's DirectX implementation   

Gripe 1:
I maintain HTML files for my own use on my own desktop. My homepage is a 
simple HTML file with many links to other pages on my computer and URLs to 
pages on the Internet. After I've browsed a while and return to my home page, 
IE brings up a very pesky alert warning me that DirectX content on my home 
page will be blocked. In order to turn off the flashing notice, I have to 
open a window, tell it to "allow blocked content", and then tell it "Yes, I 
really want to allow blocked content.”  All this when my home page HAS NO 
DIRECT X content at all! 

IE should not bother telling me it won't do something if it can't happen in 
the first place.

Gripe 1 Corollary:
This occurs periodically through out my browsing session. Even though he 
home page has not been changed, the pesky warning will popup again, and I 
will have to clear it again.  Dumb, dumb, dumb!

Gripe 2:
I really dislike the way DirectX is used by most web sites. So normally I 
keep is disabled and enable it only for specific websites. (It would be nice 
if I could keep a list of web sites I consider as “OK for DirectX.”) When 
DirectX is disabled, and a web site “wants” it, evidently the web site is 
told it’s not installed. Sites will then keep asking me to install it. 
Sometimes they even manage to trigger a download and install session.

IE should do a better job of distinguishing between “disabled” and “not 
installed.” It should not be asking me to install something that is already 
installed.

date: Fri, 12 Oct 2007 09:59:01 -0700   author:   Dorsey