SCRIPT28: Out of stack space

Question

Using JDeveloper 11.1.2.3 and JHeadstart. With IE9 (9.0.8112.16421), the following error occurs:
SCRIPT28: Out of stack space
core-11.1.2.3.0-2247.js, line 192 character 200
SCRIPT28: Out of stack space
boot-11.1.2.3.0-2247.js, line 172 character 187
This is followed by IE9 hanging indefinitely. Here is an overview of the screen:
In Chrome and FF, when the user clicks the "Care Team" region (shown above as PPR using hidden button), it calls a hidden button to remove the tabs and replace the page content. The resulting page resembles:
As you can see, the menu tabs are gone and the page content is refreshed. The hidden button has an ID of menu1CareTeamButton and is inside a panelBox with a clientListener:
      <af:clientListener method="showCareTeamContext" type="click"/>
      <af:commandButton id="menu1CareTeamButton" text="CareTeam" action="patientShell:CareTeam"
                        visible="false">
        <af:setActionListener from="PatientCareTeam" to="#{jhsDynamicMenu.currentLevel1MenuItemName}"/>
      </af:commandButton>
The JavaScript function is straightforward enough:
  function showCareTeamContext(actionEvent) {
    // Hack to find the hidden menu1CareTeamButton. This forces the button's action to fire
    // whenever the care team region is clicked.
    document.getElementById("pt:menu1CareTeamButton").click();
The menu1CareTeamButton has the following partialTriggers:
        <f:facet name="pageContent">
          <af:region id="mr" value="#{bindings.mainRegion.regionModel}"
                     partialTriggers="::Menu2 ::pendingChangesDialog ::menu1CareTeamButton ::CareTeamCloseButton"/>
        </f:facet>
      </af:pageTemplate>
            <af:navigationPane id="Menu2" hint="tabs"
                               partialTriggers="Item2 ::pendingChangesDialog ::mg:Menu1 ::menu1CareTeamButton ::CareTeamCloseButton"
                               rendered="#{attrs.showMenu2}">
Everything works flawlessly in Chrome and Firefox. IE9 fails.
Any ideas why?

Answer 1

Hi,
can you provide a test case that can be run stand alone (with no dependency to your project)? If so then this might be filed as a bug. If you have a customer support contract then you can file it yourself. If not you can send me a mail with the testcase in a zip (rename it unzip) and I file it for you. However, note that when i file the bug then it gets filed but you wont have a handle to check the bug status.
Note that the following line is not recommended to use with ADF Faces and there exist an ADF Faces JavaScript API that allows you to do the same but just not from making assumption about the rendered output (in a next release for example your code may break if the rendered output changes)
document.getElementById("pt:menu1CareTeamButton").click();
See this paper for how to do it properly: http://www.oracle.com/technetwork/developer-tools/jdev/1-2011-javascript-302460.pdf
You will also notice that instead of a hidden button, you could use af:serverListener to invoke server side Java to perform actions on your UI. This said, still chances are that IE is the cause of failure. Ensure you don't run this browser in IE compatibility mode but native.
Frank