I would expect the Seam team to have to fix this for Seam 1.3, when the RI will become the standard Seam JSF implementation. The problem is definitely that the RI more often emits a content-type of application/xhtml+xml for XHTML pages, which Firefox tries to parse as XHTML. Arguably this is just bad -- it actually breaks GWT, for instance, and XHTML 2.0 seems to be dead in the water.
In Facelets you can add a wrapper f:view tag with attribute contentType="text/html" to override this in some situations. Not sure if this will work for the itext PDF pages, but it might be worth a shot. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4042255#4042255 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4042255 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
