You must enable extensions for the application that contains the JavaScript and use the Classic Agent to record dynamic popup menus.
If you want your action-based recordings to contain references to window identifiers instead of dynamic instantiations, first record the window declarations for the pages with DHTML popup menus. There are various techniques used to build DHTML popup menus and their menu hierarchies. The techniques you use affect what Silk Test Classic sees when recording window declarations. You may find that once a page is completely loaded in the browser, all of the menus and submenus are recognized immediately by Silk Test Classic. Other times, in order for the menus and submenus to be completely seen in the Record Window Declarations dialog box, you may need to expose some or all of the menus and submenus by moving the mouse over the menu items.
Typically when you record actions, the recorder ignores mouse movement events, which are set in the Ignore Mouse Move Events text box of the Recorder Options dialog box. However, the recorder generates MoveMouse() method calls as you expose popup menus. Those calls are necessary to ensure that when you play back the script, Silk Test Classic exposes the menus as it navigates through them. The MoveMouse() calls contain coordinates because the hot spot of the item used to expose the menu may not be the entire rectangle for that item. Therefore, Silk Test Classic cannot assume that moving the mouse to the default spot, which is the upper-left corner of the rectangle for the item, will actually expose the menu.