Use CancellationFlag instead of Lock in PostHelper

XWalkExtensionThreadedRunner have a helper object that runs jobs in
another thread. When threaded runner goes down, we want to
invalidate (cancel) that helper object.

This commit change from using a Lock and changing the runner_ value
inside the helper to simply use CancellationFlag (which boils down to an
atomic operated value).
[Devtools] Show right message when App is inspected already.
To correct a HTML/CSS coding error in Devtools discovery page
Fix color chooser browser test failed on Aura

It's because that after chromium's change,
views::ColorChooserView::OnColorChanged will not be counted as
user-interacted change, and will not send color change ipc to
render side.

So for test, only trigger OnColorChanged is not enough, trigger
OnSaturationValueChosen also to simulate a real color selection.
[Android] Fix unnormalized asset URI accessing issue in AndroidProtocolHandler.

In some case, html file may contain unnormalized URIs with duplicate slashes,
for example: "file:///android_asset/path//asset_file.html",
It causes AndroidProtocolHandler can't read the asset data, so remove the
duplicate slashes before reading asset.

BUG=https://github.com/crosswalk-project/crosswalk/issues/599
Polish sample application for xwalk on Android

The origin sample app's font is too small to read.
Also add the hello-world icon for it.
Fix that assets' update will not trigger template app's rebuild

In chromium, most of the cases using assets is for paks, which
will have another step to copy built paks into product folder
as dependency of the apk target. In such case, if pak file updated,
the copy step will be triggered and the apk will rebuild also.

For template app, we are providing normal assets other than paks,
which java_apk.gypi doesn't handled well. I open an upstream bug
for this at https://code.google.com/p/chromium/issues/detail?id=288498.

As temperally solution, this patch added all assets for template
app to "addition_inputs_list" to make apk target aware of their
change.

BUG=https://github.com/crosswalk-project/crosswalk/issues/605
mac: compile

[chromium-style] Complex constructor has an inlined body.
[chromium-style] Complex destructor has an inline body.
[chromium-style] Complex class/struct needs an explicit out-of-line destructor.
[chromium-style] Classes that are ref-counted should have explicit destructors that are declared protected or private.

http://www.chromium.org/developers/coding-style/chromium-style-checker-errors
Merge pull request #625 from poussa/mac-compile-4

mac: compile
Copy Chromium extension protocol handler and extension resource implementation

application/browser/application_protocols.* are copied from
chrome/browser/extensions/extension_protocols.*,
application/common/application_resource.* are copied from
extensions/common/extension_resource.*.
Add app URI scheme support

Ref to spec: http://app-uri.sysapps.org/. Removed unwanted features from
application_protocols.cc, and ApplicationProtocolHandler will bind with the
current running Application object and handle URL requests by creating new
URLRequestApplicationJob in IO thread. Changed URLRequestApplicationJob response
implementation so that response will return in a manner akin to a HTTP GET
request which is defined in the spec's section 6.4.
Merge pull request #438 from seanlong/master

Add app URI scheme support
Merge pull request #603 from wang16/sample_app

Polish sample application for xwalk on Android
Merge pull request #598 from sqliu/otcshare-fix-asset-uri-norm

[Android] Fix unnormalized asset URI accessing issue in AndroidProtocolHandler
Merge pull request #600 from wang16/aura

Fix color chooser browser test failed on Aura
Update README.md

Fix links.
Create a ModuleSystem even for blank pages

We assumed that a v8::Context associated with a frame that were pointing
to "about:blank" was never reused when visiting other URL. This
assumption is incorrect, there are situations (like the cases triggered
by the bugs linked) that the v8::Context is reused to the page loaded.

Since the frame URL can change from "about:blank" to something else
between the calls DidCreateScriptContext() and
WillReleaseScriptContext(), we can't rely on that information. The crash
was caused by assuming that if the URL wasn't blank at
WillReleaseScriptContext() time, we had a module.

The intent of not creating module system for blank pages was to avoid
unnecessary work. This will be accomplished in the future by other means
like avoiding to load the JavaScript code that's not used.

Fixes #626 and #602.
Change ContextDestruction test to be less picky about titles

For the test move forward, we depended on the exact sequence of
instances being created. We can cover the same behavior (which is
instances will be created and not reused), without having to indicate
this in the title.

This allows us to be be lax about the exact number of instances created
now, until we add support for loading instances on demand ("lazy loading
of instances").
Automated test for issue 602

This adds a reduction of the problem identified in
https://github.com/crosswalk-project/crosswalk/issues/602 to our
browsertests. In summary: we should not crash when an empty iframe have
document.write() called for it. See comments in the added test for
details.
Replace old icon with new one for Linux/Windows