2 ms·
The feature was called DHTML Behaviors. Here's an introduction from 2000: http://msdn.microsoft.com/en-us/subscriptions/ms531079(v=vs.85).aspx http://msdn.micr
by pavlov 14y ago
The feature was called DHTML Behaviors. Here's an introduction from 2000:
http://msdn.microsoft.com/en-us/subscriptions/ms531079(v=vs.85).aspx http://msdn.microsoft.com/en-us/subscriptions/ms531079(v=vs....
Back then everything needed to tie into Win32 somehow, so of course they introduced Binary Behaviors:
http://msdn.microsoft.com/en-us/library/aa753685(v=vs.85).aspx http://msdn.microsoft.com/en-us/library/aa753685(v=vs.85).as...
"A Binary Element Behavior (or binary behavior) is a Component Object Model (COM) object loaded by a Web page and assigned to an element type in the page—either a custom element tag or an existing HTML tag. The COM object is then able to customize the behavior of the tag by implementing the IElementBehavior interface. Customizations include any options available to scripted behaviors and more advanced behaviors such as Windows Graphics Device Interface (GDI) rendering.
Because a binary behavior is a COM object, a binary behavior can execute any code after loading. For that reason, the security profile of a binary behavior is very similar to that of a Microsoft ActiveX control, and the same security considerations apply. Binary behaviors, like ActiveX controls, run with the security credentials of the user running the browser process. This means a binary behavior cannot only render to the screen, it can also potentially access local files, configuration settings, or network resources. Accessing a page that loads a malicious binary behavior presents a considerable security risk."