We were having a problem with Safari and Chrome rendering our JSF pages; all the content was available, but for some reason they refused to load any of the external links to stylesheets, javascript etc. They also refused to render any markup; in fact, all they would show was all the page "content" in the default text.
Further investigation (using fiddler) made it apparent that the pages were being served with the "application/xhtml+xml" when our page templates all had an html 4.01 strict doctype. This caused the WebKit browsers to ignore any links to external assets while Firefox and IE seemed to render the page as expected.
We discovered that creating templates that looked like (where the contentType is specified inside the f:view tag as early as possible) seemed to solve the issue:
Subscribe to:
Post Comments (Atom)
Blog Archive
-
▼
2009
(37)
-
▼
June
(10)
- Daisy CMS - connecting a JMS listener to the repos...
- Daisy CMS - customising the footer of the editor p...
- Daisy CMS - allowing attributes in the SimpleDocum...
- JSF - ensuring your [xhtml] pages load with a text...
- Eclipse Galileo (3.5): Creating and running a JSF ...
- Using Eclipse Galileo to develop JSF applications ...
- SVN Web view - looking at older revisions
- Notes on setting up mod_proxy on apache 2.2 for pr...
- Addressing stability issues when running Eclipse 3...
- Forcing glassfish 2.1 to start-up with JDK1.6 (OSX)
-
▼
June
(10)
No comments:
Post a Comment