-
1. Re: IE 9 support for Richfaces 3.x branch
hollow Oct 20, 2010 1:38 PM (in response to gonzalad)First you have to ask the million dollar question.. will Richfaces ever work...
-
2. Re: IE 9 support for Richfaces 3.x branch
ilya_shaikovsky Oct 25, 2010 5:36 AM (in response to gonzalad)Hi, unfortunatelly yes, we are completelly concentrated at JSF 2 RF 4 branch currently. And we have no releases planned at all for 3.3.x community branch(only for WFK product). But it's open for community patches to provide fixes needed by you in 3.3.4-snapshot. I do not think there will be much problems. And if somebody will report that for example some simple styling should be corrected or some simple js check's to be added and will submit patch to jira - it's likelly to appears in that branch.
As about current problems - even if the 3.3.x branch was active now - we normally do not checking RF at not-stable environments. We have too wide set of stable browsers to check all the beta's available
First you have to ask the million dollar question.. will Richfaces ever work...
Hm.. want to hear more about specific problems.
-
3. Re: IE 9 support for Richfaces 3.x branch
jbalunas Oct 25, 2010 9:44 AM (in response to hollow)Not exactly a productive, or helpful answer. I would have hoped for more....
-
4. Re: IE 9 support for Richfaces 3.x branch
tonyshao Oct 25, 2010 10:36 AM (in response to ilya_shaikovsky)yes,JSF 2 RF 4 branch.
-
5. Re: IE 9 support for Richfaces 3.x branch
gonzalad Oct 25, 2010 3:12 PM (in response to ilya_shaikovsky)Thanks for the answer, we'll wait IE 9 final release and hope we'll not find too much issues then.
Thanks once more Ilya !
-
6. Re: IE 9 support for Richfaces 3.x branch
bretwil31 Jan 2, 2012 8:13 PM (in response to gonzalad)We have multiple problems with richfaces on IE9. Tried the emulation, it does not work for us. The page will only load correctly once the "browser Mode" is set using the F12 tools. Browser mode cannot be forced using http headers. This has left us in a VERY difficult situation in a production environment. We dont have time to try and port to JSF 2, RF4, and the risk is just too high. Please could the richfaces team help out in some way here. Have tried all the suggested javascript solutions with no success.
Thanks.
-
7. Re: IE 9 support for Richfaces 3.x branch
silli_p Apr 27, 2012 2:43 AM (in response to bretwil31)We have the same problems...any solution available?
-
8. Re: IE 9 support for Richfaces 3.x branch
jadtn May 19, 2012 10:09 AM (in response to gonzalad)In same case, have you found a good workaround?
It's critical, when i look in google analytics IE represent 38.18% of internet and 60% of ie use ie9!!! Millions people !! Impossible to say to users:" no no" not use ie, use chrome or firefox because actually we are in a course for a migration because our library has 1 year and is no more supported....
I think a good workaround (Servlet filter don't work it s impossible to add meta just after <head>) or anything else is welcome and urgent. Please show us Richfaces is the better choice in jsf library.
Thanks
Adrien
-
9. Re: IE 9 support for Richfaces 3.x branch
gonzalad May 19, 2012 12:30 PM (in response to jadtn)Hi Adrien,
We're using RF 3.3.3.Final, it works fine in IE9 when setting IE8 compatibility mode.
You just have to set the necessary HTTP Headers (see http://www.mat-wright.com/2011/02/internet-explorer-9-compatibility-quick.html).
I'm not at work, but it should be something like X-UA-Compatible: IE=EmulateIE8.
You can use a servlet filter for this or just modify your apache configuration (we use the first approach, but IMO the second is better since you don't have to modify your webapp).
-
10. Re: IE 9 support for Richfaces 3.x branch
jadtn May 19, 2012 4:04 PM (in response to gonzalad)Hi Gonzalad,
Thanks for the link, very interesting.
If you use a Servlet filter how do you do to put the meta just after <head> and before the meta of Richfaces?
ServletFilter:
----------------
->For ServletFilter i've try to do it (with PhaseListener also) , but the meta X-UA-Compatible is always inserted after the meta of richfaces , so it have to be the first meta after <head>
In the forum
Niraj Adhikary has same problem :https://community.jboss.org/message/57641
(etc...many other post)
->On internet i found many people who have this problem and the only workaround they found to put meta X-UA.. just after <head> is to use servlet filter and set loadScript/StyleStrategie at NONE and add explicitly the metas for richfaces in each page, I've try, it s 'functionnaly' ok but after the problem are skins and rich:page (semantic laouyt) .... http://java-dvlpr.blogspot.fr/2011/05/richfaces-and-ie8-issues-modal-panel_22.html
APACHE
-------------
->I think it is only for who use mod_jk.....(snif)
Thanks for response
Adrien
-
11. Re: IE 9 support for Richfaces 3.x branch
gonzalad May 19, 2012 7:41 PM (in response to jadtn)You just need to set HTTP header.
Try something like this (don't know if this compiles), it should work :
public class IECompatibilityFilter implements Filter { public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) { ((HttpServletResponse) response).setHeader("X-UA-Compatible", "IE=EmulateIE8"); chain.doFilter(request, response); } }
Hope this helps
-
12. Re: IE 9 support for Richfaces 3.x branch
jadtn May 20, 2012 1:14 AM (in response to gonzalad)Hi Gonzalad
Thanks for your response.
This is exactly the filter I used, but if you look in the console of IE9 n this warning is write :"HTML1115: X-UA-Compatible META tag ('IE=EmulateIE8') ignored because document mode is already finalized."
So what is the trick to put the meta before richfaces metas?
Adrien
-
13. Re: IE 9 support for Richfaces 3.x branch
gonzalad May 22, 2012 4:04 AM (in response to jadtn)Hi Adrien, sorry for the late reply.
Couldn't get my hands on a desktop with IE 9 ;(
However, you shouldn't have to set <meta> in your JSF page (setting HTTP Header with the filter should be enough).
The error : "HTML1115: X-UA-Compatible META tag ('IE=EmulateIE8') ignored because document mode is already finalized." is explained here : http://evolpin.wordpress.com/2011/02/25/ie9-compatibility-and-the-meta-tag/
It appears because your
X-UA-Compatible meta directive is not the first meta directive.
Once more, don't use the meta directive - just set the HTTP Header.
-
14. Re: IE 9 support for Richfaces 3.x branch
szseanzhang Jun 9, 2012 1:28 AM (in response to gonzalad)Thank you very much!
You just described the point exactly and solved my problem.