Problems with IE11 - Orbeon Forms 3.9.0

Hi,  
We use Orbeon Forms 3.9.0.pre.201106030300 PE and we have many problems with IE11. Could not migrate to the biggest version, because of lot modifications and certificate.
One of the problem for example is when we want to add a row of elements to a table we use Orbeon action xforms:insert
<xf:insert origin="xxforms:call-xpl('oxf:/apps/b-process/strip-namespaces.xpl', 'data', instance('detailsTemplate'), 'data')"
    nodeset="instanse('fr-form-instance')/InvoiceHeader"
      at="1"
      context="instance('fr-form-instance')"
      position="after" />
This action doesn't work under IE11 and could not find solution till now.
We try to set compatibility headers to the response : "X-UA-Compatible":"IE=EmulateIE9" when load xforms , but Orbeon overwrite the response headers.
The other problem is when you have required input field and filed the form is not refresh and the field is still required.
Could you help please ?

Hi Sonya,

My recommendations:

1. Even if you can't upgrade right now, plan doing it at some point in the near future. I know this isn't what you want to hear right now ;), but using new versions you'll benefit from new features, performance improvements, fixes, etc. Unless you're dealing with a totally legacy application, it's really worth upgrading.

2. Did you try putting <xhtml:meta http-equiv="X-UA-Compatible" content="IE=10"/>? (Since the problem is just with IE11, you can use IE10 instead of IE9 in this setting.) I am not sure how your app works, but the best place to put that is most likely in the theme, e.g. theme-plain.xsl.

https://github.com/orbeon/orbeon-forms/blob/tag-release-3.9.0-ce/src/resources/config/theme-plain.xsl

3. If you're already done changes to Orbeon Forms, you could put the patch for IE11 on the version you're using, since this is a pretty simple patch:

https://github.com/orbeon/orbeon-forms/commit/0d156deb92d57ec4714e24afe04438875683ce49

You'll let us know how it works,

Alex

Hi Alex ,
Thanks for the fast answer, it help me a lot and now it's ok IE11. For sure we should upgrade but there is a lot of changes in jar files and some of configuration files so for now we stay on that build.
Thanks :)