IE9 + RichFaces Rendering problem_问答_开发者_运维开发者技术经验分享

开发者 https://www.devze.com 2023-03-05 04:14 出处：网络

I have a web app which runs on JSF 2.0 + Richfaces 3.3.3. Looks great on all browsers except IE9. In IE9 without compatibility mode (With, no problem) it looks something like this (ignore blacked out

I have a web app which runs on JSF 2.0 + Richfaces 3.3.3. Looks great on all browsers except IE9.

In IE9 without compatibility mode (With, no problem) it looks something like this (ignore blacked out text):

IE9 + RichFaces Rendering problem

Notice how all the components are framed and CSS is ignored (Not seen?)

The JSP looks like this (Only relevant stuff):

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf8">
<link rel="stylesheet" href="css/pageStyle.css" type="text/css" >
</head>

<body>
...
</body>

The css is located at C:\apache\tomcat\webapps\MyWebApp\css\pageStyle.css

Anyone got any idea? Thanks!

UPDATE Did some research with 'developer tools' by capturing packets with the network tab. The css file is sent with Type=text/html instead of text/css.开发者_高级运维 I guess that's the problem according to this question.

But I still don't know why this happens. As you can see, the file type is clearly marked as type="text/css in the <link> tag.

Another interesting observation - examining the same object in Chrome Developer Tools, the content-type is text/css so maybe its a IE9 bug. I'm confused...

RichFaces 3.x does not support IE9 (and there are no plans to introduce it), refer to this topic: http://community.jboss.org/thread/156720

You can upgrade to RF 4,

or implement a filter to force IE9 to run in compatibility mode:

public void doFilter(final ServletRequest request, final ServletResponse response, final FilterChain chain) throws IOException, ServletException {
    HttpServletResponse resp = (HttpServletResponse) response;
    resp.addHeader("X-UA-Compatible", "IE=EmulateIE8");
    chain.doFilter(request, resp);
}

Richfaces 3.3 predates IE9 being out of beta so it's likely that there will be some compatibility issues since the build probably wasn't tested vs. IE9.

The good news is that you're using JSF 2 so there is no reason you can't upgrade to Richfaces 4 Final which does definitely support IE9.

That being said the version of JSF you use seems to be important as well. I'm using mojarra and in version 2.0.4 I had issues with many Richfaces components when they were reloaded with mojarra.ab (f:ajax). Upgrading to 2.1.1 seems to have resolved all of these issues and now I have Richfaces code in production that is performing well for IE9 users.

I would recommend that you take a look at an upgrade path and see if it's viable.

The problem is that IE9 needs that http response for css file has the Content-Type header defined. Your http response headers should appears like this: