This section describes troubleshooting and limitations for supporting a custom control.
You cannot select controls inside an object element on a Web page.
Workaround: Copy the HTML source code from inside the object element to another Web page and select the relevant controls from that page.
In some specific cases, when you click a control to select it, the application responds to the click (for example, by closing a drop-down menu) instead of, or in addition to, Extensibility Accelerator recognizing the selection. This sometimes makes it difficult to select a control to create rules.
Workaround: In some cases, you can click a higher HTML element in the hierarchy and then select this control from within the displayed hierarchy. In other cases you might have to manually create a rule for the control.
The Extensibility Accelerator rule editor (on the Map to Controls tab of the test object class designer) does not support selection of controls in a dialog box.
To select controls in a Web page, make sure that in Tools > Internet Options the options specified below are enabled. (Note that in some operating systems these options may be disabled by default.)
Security (Internet Zone) > Custom Level > ActiveX controls and plug-in -> Binary and script behaviors
Security (Internet Zone) > Custom Level > Scripting-> Active scripting
To enable Extensibility Accelerator to run on a custom control, running scripts must be enabled in the browser. If the browser automatically blocks running scripts when you run your application, make sure to allow blocked content before using Extensibility Accelerator its the controls.
When the Identification element in the toolkit configuration XML file includes HTMLTags elements, they are not displayed in the rule editor on the Map to Controls tab of the test object class designer.
Note: This is relevant for some of the controls in the Extensibility Accelerator sample Web 2.0 support projects.