forked from googlearchive/chromium-webview-samples
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' of https://github.com/GoogleChrome/chromium-web…
…view-samples * 'master' of https://github.com/GoogleChrome/chromium-webview-samples: Further readme tweaks and formatting Fixing up the README with images and goodness Fixing up the README with images and goodness
- Loading branch information
Showing
1 changed file
with
28 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,28 @@ | ||
chromium-webview-samples | ||
======================== | ||
Chromium WebView Samples | ||
=========================== | ||
|
||
This is a repository with useful examples for developing apps using the Chromium WebView. | ||
|
||
If you spot any issues or questions please feel free to file an issue or reach out to [@gauntface](http://www.twitter.com/gauntface). | ||
|
||
##TEXT_AUTOSIZING | ||
|
||
From KitKat and above, there will no longer be support for [SINGLE_COLUMN or NARROW_COLUMN layout algorithms](http://developer.android.com/reference/android/webkit/WebSettings.LayoutAlgorithm.html). | ||
|
||
However a new layout algorithm [TEXT_AUTOSIZING](http://developer.android.com/reference/android/webkit/WebSettings.LayoutAlgorithm.html) was added and *textautosizing-example* contains a basic example to see the affects of the algorithm. | ||
|
||
<p align="center"> | ||
<img src="http://i.imgur.com/03c0isb.png" alt="Image Show off TEXT_AUTOSIZING" /> | ||
</p> | ||
|
||
##Touch Events in the WebView | ||
|
||
In the older version of the WebView developers didn't need to implement the *touchcancel* event, although it's good practice to do so. | ||
|
||
In the Chromium WebView it's important to implement the *touchcancel* event as certain scenarios will trigger a *touchcancel* event instead of a *touchend* event, where they wouldn't before (i.e. a user scrolls off of an element or e.preventDefault() isn't called in the *touchstart* event). | ||
|
||
The *web-touch-example* contains a simple app which uses touch to move an element and reveal a little Android. | ||
|
||
<p align="center"> | ||
<img src="http://i.imgur.com/ffz4gkV.png" alt="Image of WebView Touch Example" /> | ||
</p> |