Patching RichFaces 3.3.3 AJAX.js for IE11

Comments

6 responses to “Patching RichFaces 3.3.3 AJAX.js for IE11”

1. 

   Victor Zamora

   April 6, 2018

   Thanks a lot!!! This patch saved a major problem in a big project.
   Thanks!

   Reply
2. 

   Ravi

   August 23, 2017

   Hi,
   I have applied the same thing but with richfaces-3.2.1.GA.jar.
   I am getting ‘SCRIPT28: Out of stack space’
   File: AJAX_IE9fix.js, Line: 619, Column: 33

   Do you have any idea or any solution for this ?

   Reply
3. 

   Volkert de Buisonjé

   March 21, 2016

   Hi! Thanks for this useful information!

   Note however, that your IE detection code for Sarissa._SARISSA_IS_IE9 now fails again in Microsoft Edge.

   I adapted your fix a bit and made it work with Microsoft Edge as well.

   Due to lack of actvity at the official Sarissa project web site, I started a 0.9.9.7-SNAPSHOT branch of Sarissa at https://github.com/volkertb/sarissa/tree/0.9.9.7-SNAPSHOT. It is not intended as an official fork. I just prefer working with Git and GitHub over CVS and SourceForge (even though SourceForge also supports Git these days).

   This new branch is based on the latest CVS trunk from the upstream Sarissa repository on SourceForge, which apparently includes some additional fixes since the 0.9.9.6 release, even though it was still given the version 0.9.9.6 in the source code, which was frankly confusing. Therefore I bumped it up to 0.9.9.7-SNAPSHOT in my branch, since no official version after 0.9.9.6 has been released yet. On top of that, my branch includes the Sarissa-specific fixes you shared, as well as my adaption to make it work with Microsoft Edge as well. I also applied a XMLSerializer wrapping code fix that I adapted from the fix for RichFaces issue NXBT-677, original commit https://github.com/nuxeo/richfaces/commit/5afdc76a78c18ccc965af04dea79ab7cfec96bb3

   Feel free to check it out, provide feedback an/or create pull requests with further improvements! :-)

   Reply
   1. 

      Patrick

      March 21, 2017

      Hi,

      thanks for that fix.I just have one question regarding the replacePage function.

      A4J.AJAX.replacePage = function(req){
      if(!req.getResponseText()){
      LOG.warn(“No content in response for replace current page”);
      return;
      }
      LOG.debug(“replace all page content with response”);
      var isIE = _SARISSA_IS_IE;

      The last line is wrong in my opinion and needs to be
      var isIE = Sarissa._SARISSA_IS_IE;

      I think there is a mission sarissa reference.

      Reply
4. 

   Russ

   January 18, 2016

   >> Although it’s 2015 using JSF 1.2 and RichFaces 3.3.3 is still working quite nicely :)
   I’m curious though whether you’ve noticed a delay on IE11 loading pages where r:dropDownMenu, r:dataTable and/or r:column were used?

   We’re using a similar stack (yay for early adopters – we were still on 3.2.2 because we thought the next step was JSF2) and since the menu was on every page our users were a little unhappy to get a 5 second delay on each page. I determined the issue was related to RichFaces and swapped out the menu for a DHTML version we abandoned in 2008 and modernized it a bit; but we still have a few pages that experience the delay. Wondering whether we’re the only ones.

   Reply
   1. 

      Marko

      January 18, 2016

      Can’t say that I’ve noticed delays particularly with IE 11 when using RichFaces 3.3 and JSF 1.2. We have dropdownmenus but use Tomahawk’s datatables as RF datatable’s didn’t work well with large datasets (slow, would’ve needed custom paging).

      Fortunately I’ve nowadays left that legacy project behind and moved on to modern UI stack :)

      Reply