Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid's WebKit and JavaServerFaces
    primarykey
    data
    text
    <p>I wonder why WebKit trying to render my page as XML instead of HTML.. I tried this issue (via emulator and real device) for all available Android SDK versions and all OK only since Android 2.3.4 (API 10) with WebKit/533.1 One more strange thing is browser versions:</p> <p>Android 2.2.1 has WebKit/533.1 and Android 2.3.4 also has WebKit/533.1</p> <p>So, my page does not want to render in 2.2.1 with 533.1, but all good in 2.3.4 with the same 533.1?? Page code is simple:</p> <pre><code>&lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt; &lt;html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html" xmlns:c="http://java.sun.com/jsp/jstl/core"&gt; &lt;head&gt; &lt;meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /&gt; &lt;meta http-equiv="Cache-Control" content="no-cache" /&gt; &lt;title&gt;Title&lt;/title&gt; &lt;/head&gt; &lt;body&gt; ... &lt;/body&gt; &lt;/html&gt; </code></pre> <p>Google says I must declare Content-Type header as text/html, but it has been already declared. What I can see with LiveHTTPHeaders (Firefox add-on) while requesting that JSF page:</p> <pre><code>HTTP/1.1 200 OK X-Powered-By: Servlet/3.0 JSP/2.2 (GlassFish Server Open Source Edition 3.1.1 Java/Sun Microsystems Inc./1.6), JSF/2.0 Server: GlassFish Server Open Source Edition 3.1.1 Content-Type: text/html;charset=UTF-8 Content-Length: 1559 Date: Tue, 13 Mar 2012 19:50:13 GMT </code></pre> <p>Did you meet such kinds of issues?</p> <p>Thanks, Vladimir</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload