Lines Matching full:webkit
42 <p>Android 4.4 (API level 19) introduces a new version of {@link android.webkit.WebView} that is
44 {@link android.webkit.WebView} performance and standards support for HTML5, CSS3, and JavaScript
45 to match the latest web browsers. Any apps using {@link android.webkit.WebView} will inherit these
49 to {@link android.webkit.WebView} that you should be aware of if you set your
55 targetSdkVersion}</a> is set to "18" or lower, {@link android.webkit.WebView} operates in
67 {@link android.webkit.WebView} in Android 4.4, you can enable remote debugging through
69 {@link android.webkit.WebView#setWebContentsDebuggingEnabled setWebContentsDebuggingEnabled()}.
70 This new feature in {@link android.webkit.WebView} allows
72 a {@link android.webkit.WebView}. For more information, see <a
81 <p>If you serve content to your {@link android.webkit.WebView} based on the user agent, you should
90 do not want to instantiate {@link android.webkit.WebView}, you should use
91 the static method, {@link android.webkit.WebSettings#getDefaultUserAgent
93 {@link android.webkit.WebView}, you may instead want to use
94 {@link android.webkit.WebSettings#getUserAgentString getUserAgentString()}.</p>
101 <p>If you call methods on {@link android.webkit.WebView} from any thread other than your app's
127 <p>You can instead use a new method, {@link android.webkit.WebView#evaluateJavascript
136 <p>The new {@link android.webkit.WebView} applies additional restrictions when requesting resources
138 {@link android.webkit.WebViewClient#shouldOverrideUrlLoading shouldOverrideUrlLoading()} or
139 {@link android.webkit.WebViewClient#shouldInterceptRequest shouldInterceptRequest()}, then
140 {@link android.webkit.WebView} invokes them only for valid URLs.</p>
147 <p>For example, the new {@link android.webkit.WebView} may not call your
148 {@link android.webkit.WebViewClient#shouldOverrideUrlLoading shouldOverrideUrlLoading()} method
155 <li>If you loaded the page by calling {@link android.webkit.WebView#loadData
156 loadData()} or {@link android.webkit.WebView#loadDataWithBaseURL
158 {@link android.webkit.WebViewClient#shouldOverrideUrlLoading shouldOverrideUrlLoading()} callback
161 When you use {@link android.webkit.WebView#loadDataWithBaseURL
164 <li>If you loaded the page by calling {@link android.webkit.WebView#loadUrl
165 loadUrl()} or provided a valid base URL with {@link android.webkit.WebView#loadDataWithBaseURL
167 {@link android.webkit.WebViewClient#shouldOverrideUrlLoading shouldOverrideUrlLoading()} callback
180 {@link android.webkit.WebViewClient#shouldOverrideUrlLoading shouldOverrideUrlLoading()} method
199 {@link android.webkit.WebView#loadDataWithBaseURL loadDataWithBaseURL()} and set a base URL
220 <p>Previously, {@link android.webkit.WebView} supported a viewport property called
232 equal to the {@link android.webkit.WebView} height, it would be set to "device-height". However,
233 when running in the new {@link android.webkit.WebView}, the width or height value is adhered and
234 the {@link android.webkit.WebView} zooms in to fill the screen width.</p>
239 <p>Previously, if you included multiple viewport tags in a web page, {@link android.webkit.WebView}
241 In the new {@link android.webkit.WebView}, only the last viewport is
247 <p>The methods {@link android.webkit.WebSettings#getDefaultZoom()} and
248 {@link android.webkit.WebSettings#setDefaultZoom setDefaultZoom()} for getting and setting
261 {@link android.webkit.WebSettings#setUseWideViewPort setUseWideViewPort()} to ensure the page
279 {@link android.webkit.WebView} will also override a CSS setting for {@code background-size}
307 In the new {@link android.webkit.WebView}, these return a value based on CSS pixels.</p>
314 JavaScript binding</a> to query the pixel size from the {@link android.webkit.WebView} itself.</p>
323 <p>The {@link android.webkit.WebSettings.LayoutAlgorithm#NARROW_COLUMNS} value for {@link
324 android.webkit.WebSettings.LayoutAlgorithm} is not be supported in the new {@link
325 android.webkit.WebView}.</p>
343 <li>Use the new {@link android.webkit.WebSettings.LayoutAlgorithm#TEXT_AUTOSIZING} layout
347 {@link android.webkit.WebSettings.LayoutAlgorithm#TEXT_AUTOSIZING} algorithm may be a
348 suitable alternative to {@link android.webkit.WebSettings.LayoutAlgorithm#NARROW_COLUMNS}.</p>
352 <p>Additionally, the {@link android.webkit.WebSettings.LayoutAlgorithm#SINGLE_COLUMN} value—which
354 android.webkit.WebView}.</p>
361 <p>If your web page is directly handling touch events in a {@link android.webkit.WebView},
374 {@link android.webkit.WebView} assumes you don't want to consume the touch events).</li>
