1 Reply Latest reply on Jul 25, 2013 2:20 PM by 5b848516-da35-421a-a5f5-d14bcd87fc3c

    Apex Migration (3.2 -> 4.2) issues with recent browsers


      Dear Apex Users,

      I need your help regarding an unbelievable issue upgrading my Apex application:


      * Oracle 11gR2

      * Apex 4.2

      * OHS

      * Apex application created with Apex 3.2.2


      Issue Description:

      • First problem: A list region is not displayed in recent browsers (IE10, FF22). ok with old browser (IE9, FF17 ESR)
      • Cache is disabled for Apex and OHS.
      • Note: The app was ok with APEX 3.2.2 with FF22 and IE10



      • Update of page headers (in page template)
        • Add <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
        • KO: No change (headers not changed, list not displayed) for IE10 and FF22
        • OK: Headers updated with IE9 and FF17 ESR
      • According to firebug DOM explorer, HTML code of the list region is not in the source code for FF22. The same for IE10.
      • Switch page template (from our custom template to the "No Tabs - Right Sidebar" page template of "Cloudy" theme), re-save display points for each regions of the page (including the list)
        • KO: Template not changed with IE10 and FF22
        • OK: New templated is used with IE9 and FF17ESR
      • Add a "Test" HTML region to this page
        • KO with FF22 and IE10, test region is not in the page
        • OK with IE9 and FF17 ESR, the test region is displayed
      • Add a "Test" page to the current application
        • KO with IE10 and FF22: internal error
      is_internal_error: true
      apex_error_code: APEX.PAGE.NOT_FOUND
      ----- PL/SQL Call Stack -----
      object      line  object
      handle    number  name
      0x11cae9080       556  package body APEX_040200.WWV_FLOW_ERROR
      0x11cae9080       607  package body APEX_040200.WWV_FLOW_ERROR
      0x11cae9080       911  package body APEX_040200.WWV_FLOW_ERROR
      0x1264e72e0      5537  package body APEX_040200.WWV_FLOW
      0x11ccc37e8       249  procedure APEX_040200.F
                  0x11ccda3f0        35  anonymous block
        • OK with IE9 and FF17 ESR



      • Why "old pages" are served with IE10 and FF22?
      • Is there a browser dependent configuration (especially for the cache mechanism)?
      • What am I doing wrong?