ICEfaces
  1. ICEfaces
  2. ICE-10685

icecore:navigationNotifier fails in IE11

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: EE-3.3.0.GA_P03
    • Fix Version/s: EE-3.3.0.GA_P03
    • Component/s: ICECORE-Components
    • Labels:
      None
    • Environment:
      EE-3.3.0.GA_P03 revision 44672
      Browsers: IE11
      Server: Tomcat7
    • Affects:
      Documentation (User Guide, Ref. Guide, etc.), Compatibility/Configuration

      Description

      icecore:navigationNotifier fails in IE11:
      the counter is not increased, and a server error occurs each time when navigating back and forward in the browser;
      not an issue in IE7/8/9/10, FF34 or Chrome42; not an issue on IF4 trunk rev. 44662.

      After restarting Tomcat a few times the server error stopped occurring when testing locally (it still occurs when testing remotely), but the counter still fails to increase.

      QA test app:
      http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces2/Sparkle/Nightly/navigationNotifier

      May 12, 2015 4:19:01 PM com.sun.faces.application.resource.ResourceHandlerImpl logMissingResource
      WARNING: JSF1064: Unable to find or serve resource, jsf.js, from library, javax.faces.
      May 12, 2015 4:19:01 PM com.sun.faces.application.resource.ResourceHandlerImpl logMissingResource
      WARNING:
      ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error
              at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:406)
              at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:480)
              at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:366)
              at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:431)
              at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:419)
              at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:91)
              at java.nio.channels.Channels$WritableByteChannelImpl.write(Channels.java:458)
              at com.sun.faces.application.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHand
      lerImpl.java:283)
              at javax.faces.application.ResourceHandlerWrapper.handleResourceRequest(ResourceHandlerWrapp
      er.java:125)
              at javax.faces.application.ResourceHandlerWrapper.handleResourceRequest(ResourceHandlerWrapp
      er.java:125)
              at javax.faces.application.ResourceHandlerWrapper.handleResourceRequest(ResourceHandlerWrapp
      er.java:125)
              at org.icefaces.application.ResourceRegistry.handleSessionAwareResourceRequest(ResourceRegis
      try.java:147)
              at org.icefaces.impl.application.SessionAwareResourceHandlerWrapper.handleResourceRequest(Se
      ssionAwareResourceHandlerWrapper.java:40)
              at javax.faces.application.ResourceHandlerWrapper.handleResourceRequest(ResourceHandlerWrapp
      er.java:125)
              at javax.faces.application.ResourceHandlerWrapper.handleResourceRequest(ResourceHandlerWrapp
      er.java:125)
              at org.icefaces.impl.push.DynamicResourceDispatcher.handleResourceRequest(DynamicResourceDis
      patcher.java:78)
              at org.icefaces.impl.application.WindowScopeManager.handleSessionAwareResourceRequest(Window
      ScopeManager.java:71)
              at org.icefaces.impl.application.SessionAwareResourceHandlerWrapper.handleResourceRequest(Se
      ssionAwareResourceHandlerWrapper.java:40)
              at javax.faces.application.ResourceHandlerWrapper.handleResourceRequest(ResourceHandlerWrapp
      er.java:125)
              at org.icefaces.impl.push.servlet.ICEpushResourceHandler$ICEpushResourceHandlerImpl.handleRe
      sourceRequest(ICEpushResourceHandler.java:241)
              at org.icefaces.impl.push.servlet.ICEpushResourceHandler.handleResourceRequest(ICEpushResour
      ceHandler.java:128)
              at org.icefaces.impl.application.SessionTimeoutMonitor.handleSessionAwareResourceRequest(Ses
      sionTimeoutMonitor.java:63)
              at org.icefaces.impl.application.SessionAwareResourceHandlerWrapper.handleResourceRequest(Se
      ssionAwareResourceHandlerWrapper.java:40)
              at javax.faces.application.ResourceHandlerWrapper.handleResourceRequest(ResourceHandlerWrapp
      er.java:125)
              at javax.faces.application.ResourceHandlerWrapper.handleResourceRequest(ResourceHandlerWrapp
      er.java:125)
              at javax.faces.application.ResourceHandlerWrapper.handleResourceRequest(ResourceHandlerWrapp
      er.java:125)
              at javax.faces.application.ResourceHandlerWrapper.handleResourceRequest(ResourceHandlerWrapp
      er.java:125)
              at org.icefaces.impl.application.AuxUploadResourceHandler.handleResourceRequest(AuxUploadRes
      ourceHandler.java:82)
              at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591)
              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j
      ava:305)
              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

              at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
              at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
              at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
              at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
              at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
              at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:953)
              at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
              at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
              at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:102
      3)
              at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.jav

        Activity

        Carmen Cristurean created issue -
        Carmen Cristurean made changes -
        Field Original Value New Value
        Summary iceocre:navigationNotifier fails in IE11 icecore:navigationNotifier fails in IE11
        Carmen Cristurean made changes -
        Fix Version/s EE-3.3.0.GA_P03 [ 11572 ]
        Ken Fyten made changes -
        Assignee Mircea Toma [ mircea.toma ]
        Assignee Priority P2 [ 10011 ]
        Ken Fyten made changes -
        Assignee Priority P2 [ 10011 ] P1 [ 10010 ]
        Hide
        Mircea Toma added a comment -

        Ported back new implementation that uses HTML5 features to detect back/forward navigation.

        Show
        Mircea Toma added a comment - Ported back new implementation that uses HTML5 features to detect back/forward navigation.
        Mircea Toma made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Hide
        Mircea Toma added a comment -

        Yes, it is. Please see ICE-10116 .

        Show
        Mircea Toma added a comment - Yes, it is. Please see ICE-10116 .
        Hide
        Carmen Cristurean added a comment - - edited

        Verified on EE-3.3.0.GA_P03 tag revision 44730, and with Jenkins Build#8 in IE10/11, FF34, Chrome42.

        Show
        Carmen Cristurean added a comment - - edited Verified on EE-3.3.0.GA_P03 tag revision 44730, and with Jenkins Build#8 in IE10/11, FF34, Chrome42.
        Hide
        Ken Fyten added a comment -

        Re-opened.

        We'll need to revert this change as it is more important for EE 3.3. P03 to retain the existing support for older IE 7/8/9 browsers for icecore:navigationNotifier than to support IE11 instead of them.

        IE 11 being more of an emerging browser than the others, certainly in the context of existing EE 3.3. application deployments justifies this.

        Customers requiring IE11 support for this feature should consider EE 4.0 instead.

        Show
        Ken Fyten added a comment - Re-opened. We'll need to revert this change as it is more important for EE 3.3. P03 to retain the existing support for older IE 7/8/9 browsers for icecore:navigationNotifier than to support IE11 instead of them. IE 11 being more of an emerging browser than the others, certainly in the context of existing EE 3.3. application deployments justifies this. Customers requiring IE11 support for this feature should consider EE 4.0 instead.
        Ken Fyten made changes -
        Resolution Fixed [ 1 ]
        Status Resolved [ 5 ] Reopened [ 4 ]
        Ken Fyten made changes -
        Security Private [ 10001 ]
        Hide
        Mircea Toma added a comment -

        Reverted previous changes to still keep support for IE 7/8/9 browsers.

        Show
        Mircea Toma added a comment - Reverted previous changes to still keep support for IE 7/8/9 browsers.
        Mircea Toma made changes -
        Status Reopened [ 4 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Hide
        Mircea Toma added a comment -

        Reverted changes for the 3.3 P03 tag as well.

        Show
        Mircea Toma added a comment - Reverted changes for the 3.3 P03 tag as well.
        Ken Fyten made changes -
        Resolution Fixed [ 1 ]
        Status Resolved [ 5 ] Reopened [ 4 ]
        Hide
        Ken Fyten added a comment -

        Marking this as won't fix as we have decided to keep support for older IE browsers in lie of supporting this feature on IE11 in the EE 3.3 product for backwards compatibility reasons.

        Projects requiring IE11 support for this feature should consider using EE 4.0 instead.

        Show
        Ken Fyten added a comment - Marking this as won't fix as we have decided to keep support for older IE browsers in lie of supporting this feature on IE11 in the EE 3.3 product for backwards compatibility reasons. Projects requiring IE11 support for this feature should consider using EE 4.0 instead.
        Ken Fyten made changes -
        Status Reopened [ 4 ] Resolved [ 5 ]
        Affects Documentation (User Guide, Ref. Guide, etc.),Compatibility/Configuration [ 10003, 10002 ]
        Assignee Priority P1 [ 10010 ]
        Resolution Won't Fix [ 2 ]
        Hide
        Liana Munroe added a comment - - edited

        Tested with ICEfaces EE-3.3.0.GA_P03 Jenkins build 09 and EE-3.3.0.GA_P03 tag r44781. When using FF 34 or 24.5(ESR) browsers the counter will increase when page is reloaded. Counter should only be increased when using the back/forward buttons in the browser. This is not an issue with any other browser. ICE-10702 is open for this issue.

        Show
        Liana Munroe added a comment - - edited Tested with ICEfaces EE-3.3.0.GA_P03 Jenkins build 09 and EE-3.3.0.GA_P03 tag r44781. When using FF 34 or 24.5(ESR) browsers the counter will increase when page is reloaded. Counter should only be increased when using the back/forward buttons in the browser. This is not an issue with any other browser. ICE-10702 is open for this issue.
        Ken Fyten made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Mircea Toma
            Reporter:
            Carmen Cristurean
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: