Add myself to the AUTHORS file.
[Android] Add "--tool-path" option for make_apk_test.

Because the xwalk_app_template target will be moved out of the "out" folder
on buildbot/trybot when the feature of generating separate APK for ARM and x86 arch
is ready. So add more flexible option "--tool-path" to replace the "--build-dir"
and "--target" options for the make_apk_test.py.
[Android] Enable W3C fullscreen API support

Fullscreen API spec is at http://www.w3.org/TR/fullscreen/.
The API allows web app to switch between fullscreen/non-fullscreen
dynamically in javascript. And also the ability to fullscreen a
dom element.

For Android, Content already provide related interface in WebContentsDelegate.
Implementing the interface and bridge to XWalkWebChromeClient finally to
toggle Activity's fullscreen status.

TEST=Manual
BUG=https://crosswalk-project.org/jira/browse/XWALK-773
Bump version to 4.32.68.0
[Android] Fix the crash issue of loading app from app:// scheme.

The fixed places:
1. As the resource rquest URL was canonicalized to lowercase in
runtime core, the host name exacted from the URL may be inconsitent
with the app package name, if there is capital letter in the package
name. So convert package name to lowercase before comparing these
two strings.
2. The unpermitted resource request should not be processed. Once
such request is received, the request job should be marked as done,
and should returned from the process function at once. So add the
missing return to the related place.

BUG=https://crosswalk-project.org/jira/browse/XWALK-808
Merge pull request #1458 from gaochun/bug808

[Android] Fix the crash issue of loading app from app:// scheme
Merge pull request #1444 from junmin-zhu/toolpath

[Android] Add "--tool-path" option for make_apk_test.
Merge pull request #1398 from zhang-qing/master

Add myself to the AUTHORS file.
[Android] Support back key to exit fullscreen

Previously, there is no way to exit fullscreen if developer
doesn't provide one. And back key is used to navigate backward.

Move the handling of back key into xwalk core and try to exit
fullscreen prior to navigate backward.
Merge pull request #1446 from wang16/fullscreen_html5

[Android] Enable W3C fullscreen API support
[SysApps] Add the Storage Info data provider abstraction

This data provider was implemented differently from the CPU Info data provider.
I'm expecting the platform implementation to be more complex, so this is just an
interface.

The platform implementation should inherit from StorageInfoProvider and
provide a implementation of the static method GetInstance(). This will allow
the StorageInfoProvider[Windows|Tizen|Linux|...] to have its own attributes
and methods.
[SysApps] Make StorageInfoProvider observable

Add the Observer interface so other objects can get notifications when
a new storage is attached and detached.

It is important to remember that StorageInfoProvider must be a singleton,
so different webapps will share the same provider. This way, we don't waste
resources monitoring the same environment twice.

The provider will get a notification to start monitoring when the first observer
is added and another notification to stop monitoring when the last is removed.
[SysApps] Add a mock StorageInfoProvider

This is just a mock info provider emulating how a provider will behave in a real
life. When monitoring for file system events, it will add and remove a storage
every 1s. It will also report at least 3 non-removable storages when asked.

We could reuse this later for unit tests.
[SysApps] Implement the Device Capabilities getStorageInfo()

This patch implements the bits for retrieving the storage information. This is
not very diffirent for the getCPUInfo other than it is using a different
provider.
[SysApps] Add an method for checking if an Event is active

This is probably more straightforward than keeping booleans around
to check if there are listeners for a certain event.
[SysApps] Make DeviceCapabilitiesObject an EventTarget

This patch adds the native bits of the EventTarget. This will allow
DeviceCapabilitiesObject to get notifications when there is someone listening
for events, so we can start monitoring the filesystem by adding an observer.

It is important to notice that it will only add itself as an observer to the
StorageProviderInfo when there is actually some listener in the JavaScript side,
this way we don't do any monitoring if nobody is listening.

The EventTarget class triggers the StartEvent() method when the first listener
is added and the StopEvent() when the last listener is removed for a particular
event.
[SysApps] Make the JavaScript shim dispatch events

The first thing to be done is make the JavaScript DeviceCapabilties an EventTarget
(which is also a BindingObject). The BindingObjects are JavaScripts objects with
a link with some native object and they use a unique ID for routing messages
between them.

common.EventTarget.call(this) initializes the EventTarget and makes
this._addEvent() possible.

Now all the blanks are filled and we are good to go. The next step would be
replace the StorageInfoProviderMock with a real implementation for each platform
we support. No need to touch on anything else.
[SysApps] Implement the Device Capabilities getDisplayInfo()

This provider is missing an Observer interface for notifications
of displays being connected and disconnected. This is very likely to
be platform dependent and we might need to add platform files.

Currently we only using a static method, but I'm keeping the GetInstance()
for the display monitoring implementation.
[SysApps] Compile Chromium's StorageMonitor as a module

The StorageMonitor is almost self-contained, despite adding itself
to the Chromium's Browser Process. We should work upstream to fix that.

Meanwhile we can compile it as module (and protect the Chromium specific bits
with a flag) so we can use it as backend for the Device Capabilities
getStorageInfo() for Linux, Mac and Windows.
[SysApps] Add a data provider for Linux based on Chromium's StorageMonitor

This provider has a big chance of being generic enough to be used for Mac and
Windows. The backend for Android was not implemented yet which makes me sad.

We will have to implement a custom provider for Android (upstream maybe?).