Topmargin is an IE-specific attribute! And so are several other errors reported on the page. These were added for IE. Internet Explorer IS NOT standards-compliant, although Microsoft sometimes claims it is. And there is no link between microsoft.com being standards-compliant and IE being a browser with a good rendering. And please explain how would a switch to IIS or.NET change the situation?
There was one ActiveX exploit that used the tag without actually loading an applet, it could be used to change values in the registry. I think the hole was due to Microsoft's implementation of applets as ActiveX objects (the exploit started with )
Topmargin is an IE-specific attribute! And so are several other errors reported on the page. These were added for IE. Internet Explorer IS NOT standards-compliant, although Microsoft sometimes claims it is. And there is no link between microsoft.com being standards-compliant and IE being a browser with a good rendering. And please explain how would a switch to IIS or
There was one ActiveX exploit that used the tag without actually loading an applet, it could be used to change values in the registry. I think the hole was due to Microsoft's implementation of applets as ActiveX objects (the exploit started with )