Merge pull request #1473 from cmarcelo/extension-owners

Add Thiago Santos to extensions/OWNERS
[Extensions] Make extension namespace read-only

Extensions export their JS content under their namespace,
which is created with the extension name. That means an
extension called "xwalk.sample" will export its functions
below the "xwalk.sample" object in JS.
This patch avoids that one do things like "xwalk.sample = null",
by marking the extension namespace object as read-only whenever
an extension's code was loaded. Trying to do it, however, won't
raise any exceptions. That follows how Javascript behaves for a
snippet like:

<script>
// Returns the window object with "foo3" added to it.
Object.defineProperty(window, "foo3", {configurable: false, writable: false, value: "foooo"});

// Returns null. No exceptions are raised.
window.foo3 = null;

// Returns "foooo".
window.foo3;
</script>

We don't touch entry_points (changing their properties to read-only)
because this is something the extension writer should do him/herself
when writing the JS shim, by JS means, since we can't predict
which entry_points should be marked as read-only or not.
In other words, that is part of the extension API being implemented.

BUG=https://crosswalk-project.org/jira/browse/XWALK-605
BUG=https://crosswalk-project.org/jira/browse/XWALK-600
TEST=./out/Release/xwalk_extensions_browsertest --gtest_filter="NamespaceReadOnlyExtensionTest.*"
TEST= Also covered by TCT in the "_in_tizen" tests.
Merge pull request #1475 from jeez/extension-read-only

[Extensions] Make extension namespace read-only
Merge pull request #1426 from pozdnyakov/ApplicationProtocolHandler_supports_multi_apps

ApplicationProtocolHandler supports multi apps
Remove "Runtime" and "Dialog" extensions

Runtime extension was added as a test for our internal extension
infrastructure and is not being used neither by Android or Tizen. There
are other extensions that test this infra, so it's OK to remove.

Dialog was an experimental extension added when Crosswalk started that
served as example. When we changed to Aura backend in Linux, it stopped
working. Given that is unmaintained we are better off removing it.
Implement the screen.orientation property

This adds the property and it is ensured to be correct after
the first orientation change. Another patch will make sure it is
100% correct in all cases.
Merge pull request #1476 from kenchris/orientationprop

Implement the screen.orientation property
[Extensions] "Fix" and enable test MultipleEntryPointsExtension.MultipleEntryPoints

This test was added by commit 77bcab7bd3ba998196da6958c590af9fe32a1cd7
"[Extensions] Add tests for loading extension with multiple entry points", but
it was never enabled.

Later then, commit 76dbc259ef6e58c1667f763403201c50d4803bc5 "[Extensions] Reduce
boilerplate for external extension tests" mispelled the path for the
multiple_entry_points_extension.so.

This patch fixes this and enables this test.
Merge pull request #1474 from cmarcelo/remove-dialog-runtime-extensions

Remove "Runtime" and "Dialog" extensions
Merge pull request #1477 from jeez/entry_points-fix-test

[Extensions] "Fix" and enable test MultipleEntryPointsExtension.Multiple...
[Extensions] Add a setter callback accessor to trampolines

Prior to this patch we weren't supporting trampolines with setter
callbacks. This patch enables extensions so can implement an API
to be used like:

"window.onFooChanged = function() { foo("teste"); };"

and use window.onFooChanged as an entry point to an extension called
xwalk.sample, for instance.

BUG=https://crosswalk-project.org/jira/browse/XWALK-835
TEST=./out/Release/xwalk_extensions_browsertest --gtest_filter="MultipleEntryPointsExtension.*"
Merge pull request #1479 from jeez/lazy-load-setter-callback

[Extensions] Add a setter callback accessor to trampolines
[Android] Support using intent to launch url in core shell

It's inefficient for developers to type complex urls in core
shell for debugging and testing.
Add a broadcast receiver in core shell activity to receive
intent to launch url.
Developers can use adb to send the intent like:
adb shell am broadcast -a org.xwalk.core.xwview.shell.launch -e url <url>
[Extensions] Fix entry points for Screen Orientation Extension

After commit 856353beba8a8318c51da3d672af187d7fd58ada, entitled
"[Extensions] Add a setter callback accessor to trampolines",
we can now use screen.onorientationchange as a valid entry point.
Merge pull request #1481 from jeez/fix-screen-orientation

[Extensions] Fix entry points for Screen Orientation Extension
Fix orientation sometimes getting stuck in current orientation after unlock

While we are locked the display_.rotation() can get out of sync with the
actual device orientation, so we need to find the best orientation given
the actual orientation, not the old one.
Merge pull request #1486 from kenchris/stuck

Fix orientation sometimes getting stuck in current orientation after unlock
Make sure screen.orientation is always valid

If the orientation has not been set by the extension yet, query it
synchronously.
Merge pull request #1488 from kenchris/sync

Make sure screen.orientation is always valid
Bump version to 4.32.71.0