Add xwalk path to git ignore list
Also need to set aura::Window title

Since each DesktopNativeWidgetAura uses a sole aura::Window as its
backed, once the title of native widget gets updated, the title of
aura::Window should also be updated in addition to updating the
XWindow created by DesktopRootWindowHostX11.

BUG=https://github.com/otcshare/crosswalk/issues/191
TEST=xwalk_browsertest --gtest_filter=XWalkRuntimeTest.GetWindowTitle

Conflicts:
	ui/views/widget/desktop_aura/desktop_native_widget_aura.cc

Rework with 32.0.1700.4 code base
Aura: fix the touch event doesn't work on Tizen 3.0 issue.

Chromium uses the sourceid of a XIDeviceEvent to decide if it is orignated
from a touch device. See events_x.cc:717. However, Chromium uses deviceid to
check touch device. See touch_factory_x11.cc:158.

As X11 spec, only slave device has same sourceid and device id. So Chromium
should setup touch device list with XISlavePointer other than XIMasterPointer
device.

BUG=https://github.com/otcshare/crosswalk/issues/187
TESTS=https://github.com/borismus/MagicTouch/blob/master/samples/tracker.html

Rework with 32.0.1700.4 code base
Fix touch support issue on Tizen 2.1

On Tizen 2.1, the multi-touch support is different from the XInput2.2
approach. It extends the older Input2.1 spec to use multiple touch
devices for multiple touch points, one touch device for one touch
points. The device type name for this purpose is MULTITOUCHSCREEN which
is not defined by XInput extension.

This fix is to make Crosswalk be able to handle the new extension to
XInput2.1 by introducing a new build option 'enable_xi21_mt'. It should
be turned on for Tizen 2.1, and is exclusive to 'use_xi2_mt' option.

Rework with 32.0.1700.4 by merging commits:
  04c4575 Move ENABLE_XI21_MT definition to xwalk.
  dd82ec8 Polish the comments for enable_xi21_mt usage.
  13c4f4b Fix touch support issue on Tizen 2.1
  3ff637c Build fix linux aura without USE_XI2_MT.
  90260a3 Fix errata related to multi touch.
Fix the issue of video/audio playback with file://android_asset scheme.

The MediaPlayerBridge in Chromium accepts uri as data source, but MediaPlayer
can't handle file:///android_asset. So for such case, handle it specially.
[Tizen] Change Sandbox IPC process title.

SetProcessTitleFromCommandLine() plays a role to change process title to
absolute path of the executable with arguments that the CommandLine object has.
For example, we want gpu process title to be "<xwalk dir>/xwalk
--type=gpu-process", not "/proc/self/exe --type=gpu-process"

However, we don't want to change browser process title, because browser process
title should be web app symbolic link path, not xwalk executable absolute path.

SandboxIPC process is the process forked by browser process. We want that
SandboxIPC process title is different from browser process title. Otherwise,
Tizen task switcher misunderstands that SandboxIPC process is also web
application process.

To achieve it,
1. Browser process must not call SetProcessTitleFromCommandLine();
2. Browser process must save argv pointer to change SandboxIPC process title later.
3. SandboxIPC process also calls SetProcessTitleFromCommandLine() to change its own process title.

BUG=https://github.com/crosswalk-project/crosswalk/issues/609
[Android] Extend android install timeout to 5 minutes for testing

For android trybots, they will use emulator to run tests.
On emulator, the operation will take really a lot of time.
[Android] When running android test, try killing adb if no devices found

It randomly happens that adb devices return empty list even device
is actually connected, killing adb and restart it can fix this.

CL=https://codereview.chromium.org/24194002
[Android] Fix the render issue introduced by single process mode.

* In Chromium, single process mode is only for Android WebView, ContentShell and
its derivatives only go to the multiple process mode.
* The context design is only for multiple process mode(ContentShell/XWalk), if we
force running it with single process mode, there are issues (black regions for
video/canvas/webgl layers, and black screen for stop/restart actions). The reason
is that Android port has browser-side compositor, and the shared context in
browser-side compositor has conflicts with renderer's contexts if running in single
process mode.
* To run ContentShell/XWalk in single process mode, we have to resolve the shared
context issue between renderer/browser.

BUG=https://github.com/crosswalk-project/crosswalk/issues/516

Conflicts:
	content/browser/renderer_host/compositor_impl_android.cc
	content/browser/renderer_host/image_transport_factory_android.cc
	content/common/gpu/client/webgraphicscontext3d_command_buffer_impl.cc
	content/common/gpu/client/webgraphicscontext3d_command_buffer_impl.h

Rework with 32.0.1700.4 code base.
Use XmbSetWMProperties to set window title for i18n issue

BUG=https://github.com/otcshare/crosswalk/issues/189
Aura: enable the touch events dispatch in DesktopRootWindowHostX11
[Tizen] Change scrollbar animator

Based on patch from: Kenneth Rohde Christiansen <kenneth.r.christiansen@intel.com>

Since we have enabled overlay scrollbars we now get the desktop behavior, which means that a thin scroll indicator is always visible, which immediately grows when scrolling and shrinks (animated) back to the small size when scrolling is over.

On Tizen we want a different behavior:
a) no scroll indicator when not scrolling
b) a think scroll indicator which is slightly offset from the right viewport edge
c) the scroll indicator should fade out (animated) when the scroll is over

This patch is changing the scrollbar animator to 'fade out' and fixes 'a)' and 'c)' from the list above.

Conflicts:
	content/renderer/gpu/render_widget_compositor.cc

Rework with 32.1700.0.4 code base.
Introduce OS_TIZEN and set specific settings for Tizen platforms

This includes disabling site themed scrollbars (we use overlay
scrollbars always), enabling double tap to zoom for zoomable pages,
disable auto playing of music (a touch is needed) as well as
moving input fields into the view when focused.

It also enables the fade out scrollbars on all Tizen platforms, not
just mobile.
[Android] Enable Web Audio on x86 -- part 3

Enable the flag to let web audio work.

Conflicts:
	content/child/runtime_features.cc

Rework with 32.1700.0.14 code base.
Add GetFieldID functing to jni_help in the content for XWalk.

Introduced by src@225471
[Tizen] Camera driver integration for Tizen

On Tizen 2.1, apps/libs that want to use camera are supposed to talk to the
gst-plugin 'camerasrc'. This element in turn interacts with the camera device
via the platform-specific interfaces in addition to the standard linux 'v4l2'
interfaces. However chromium currently can only work with the 'v4l2' camera
devices. So it's unable to drive camera on Tizen. The solution is to make
chromium aware of those platform-specific interfaces.

As a result of hacking 'camerasrc', this patch minimally cherry-picked the code
snippets from it that can barely bring up the camera, and dropped other plenty
of gstreamer-related code in order to maximally keep chromium clean meanwhile.

BUG=XWALK-176
[Temp] Backport Chromium r236822.

This is required for XWALK-454 and should help with out-of-source Tizen
builds: after M32 we generate all build system-related files outside the
source tree, and the path to the linker needs to be absolute for that to
work.

Original commit message:

  Pass the gold binary to the linker using only absolute paths.

  The previous expansion using <(PRODUCT_DIR)/../.. did not work correctly
  if one was using a different build directory layout (out-of-source builds,
  or some build directory with a different number of subdirectories).

  Solve this by doing the same as the sysroot variables: stop using relative
  paths from the build directory and extract absolute paths using DEPTH.

  TEST=./build/gyp_chromium -Goutput_dir=/somewhere/else
  R=phajdan.jr@chromium.org,thakis@chromium.org,dpranke@chromium.org

  Review URL: https://codereview.chromium.org/83673002

BUG=https://crosswalk-project.org/jira/browse/XWALK-454
[Android] Allow use non Activity context to create ContentVideoView

ContentVideoView is making an assertion that the context used to create
it is an Activiy, which xwalk doesn't meet. So xwalk crashes when
trying to fullscreen a video.

Why upstream makes the assertion:
ContentVideoView will use context to getSystemService(WINDOW_SERVICE),
which requires an Activity context.

Why xwalk can work as well as break the assertion:
In xwalk case, it's using a MixContext which although the base context
is not an Activity, but the getSystemService call will be bridged to
an Activity finally.

Why can't this be upstreamed:
The real assertion is getSystemService must be called on an Activity,
upstream uses the equivalence that the context should be an Activity
is reasonable for most cases.

For more detail discussion, please refer upstream CL at:
https://codereview.chromium.org/67763004/

Since there's no easy way to detect whether the WindowManager got from
the Context is good or not, this patch to remove the assertion have
to stay in our fork.

BUG=https://crosswalk-project.org/jira/browse/XWALK-171
[SysApps] Expose ffmpeg function signatures needed by Device Capabilities API

We need these functions in to get the list of Codecs available in the
system for getAVCodecs(). If we ever fork ffmpeg, we can just remove
this patch and add the signatures directly at the ffmpeg's signature
list.
[Tizen][Performance] Enable Accelerated 2D Canvas.

If GPU context can be lost, Accelerated 2D Canvas is disabled, because there is
no way to recover Accelerated 2D Canvas when GPU crashes. Currently, only EGL
backend marks GPUInfo::can_lose_context true (means Accelerated 2D Canvas cannot
be enabled). However, interestingly, Android and ChromeOS mark it false to take
advantage of Accelerated 2D Canvas without fallback solution. They just take a
risk.

So Tizen also takes a risk like Android and ChromeOS. It is worth to do it
because performance improvement is very significant (2~3 times).

Measurement data:
1. http://www.craftymind.com/factory/guimark3/vector/GM3_JS_Vector.html
Software Canvas : 14.91 FPS
Accelerated 2D Canvas : 44.82 FPS
2. http://www.craftymind.com/factory/guimark3/bitmap/GM3_JS_Bitmap.html
Software Canvas : 17.16 FPS
Accelerated 2D Canvas : 54.58 FPS
3. http://www.craftymind.com/factory/guimark3/compute/GM3_JS_Compute.html
Software Canvas : 19.36 FPS
Accelerated 2D Canvas : 39.18 FPS

BUG=https://crosswalk-project.org/jira/browse/XWALK-531,
https://crosswalk-project.org/jira/browse/XWALK-73