Age | Commit message (Collapse) | Author |
|
Merge "Cherry-pick "ARM assembler: fix undefined behaviour in
fits_shifter"".
Change-Id: Ic1cede4c40387dff8f370a58fa5eda4ce1eb05e5
|
|
|
|
To pick up https://android-review.googlesource.com/#/c/152166/
Change-Id: I3bc3d5e75558c64430a0d6b05763bf07de637a4f
|
|
|
|
Add the nested projects as submodules, so it will continue to work once we
converted repo manifest into git submodules.
Change-Id: I2cadf23118daeaffba8f00bf7f22b06e1b812b5b
|
|
generate_trig_table and system_icu was removed for the regular
build in earlier commits.
Change-Id: I69535f135c30b75b7329f756bcec981b70ae966c
|
|
|
|
Change-Id: I72aa06e62065d848f46dfd140c897a3ffb97a171
|
|
|
|
generate_trig_table and system_icu was removed for the regular
build in earlier commits.
Change-Id: I69535f135c30b75b7329f756bcec981b70ae966c
|
|
This is a webview only fork. It will not work and probably break on
other platforms.
BUG=19958028
Change-Id: I969216e8dc152388836ad28b7808b8b1d8b6cf07
|
|
detection"
Original CL:
https://crrev.com/7a3234c9a19a38726a4a984ff12e2b406423c1d3
Original description:
[Android WebView] Provide user-initiated provisional load detection
Do not synthesize page loading events on DOM modification, if the provisional
load has been started from the API side.
It appears that a lot of apps tend to use the following scenario:
webView.loadUrl(...);
webView.loadUrl('javascript:...');
Which was triggering page loading events to be emitted. This scenario is
dubious, as no one guarantees that loading will actually finish prior to
executing javascript. But for compatibility reasons we must take it into
account and not emit page loading events for "about:blank", as it seems
that some apps do unexpected things when they receive it.
BUG=458569,469099
Note that this patch also contains bits from this commit required for changes
in AwWebContentsObserver to work:
https://crrev.com/5668d12d29ab659ad01dc0e0ffdf24f2eb5f187a
Bug: 19729876
Change-Id: I12c9610a13a382d725cc9a14fcb9879c92f1f461
|
|
|
|
Update the submodule commits to the latest versions to stop git status
showing them as modified.
Change-Id: Ifcd22ea65a147b597e92e054b10c86045224aa6b
|
|
The orientation lock code was accidentally inherited from Chrome and
doesn't actually work in WebView. Make it actually fail when JS calls
it, instead of claiming to work but doing nothing, by disabling the
screen orientation provider. This puts WebView in the same state as
desktop chrome which also doesn't set the provider. Tested that this
results in correctly reported errors when JS tries to use the API.
Bug: 19672531
Change-Id: I66a142fc50fa12db418b9465c6f29914633bd9b2
|
|
Battery status was crashing when called because the Java code in the
component was not being compiled into the webview in the android build
system. Add the missing java source directory. Battery status now works.
http://crbug.com/465366
Change-Id: I6e0f7d8d4bd0f8a284ac3e6a2a7c9e7ec1585f51
|
|
source modification (Re-land)"
Back-port of https://codereview.chromium.org/970883002/ for m40.
Original description:
[Android WebView] Synthesize a fake page loading event on page source modification (Re-land)
When a script modifies page source of a non-committed page, we need to
notify clients, so they can update the URL bar to avoid confusion.
New logic since the last attempt (https://codereview.chromium.org/924833003/):
distinguish between a "vanilla" WebView state (basically, a newly created
WebView, where no loading attempts have been made) and an "attempted to
navigate" state. In the "vanilla" state, don't fire synthesized page loading
events to avoid confusing clients. This is safe, as WebView is guaranteed to be
on a blank page.
Implementation note: we detect navigation attempts using
didStartProvisionalLoadForFrame WebContentsObserver event on the Java side. As
for popups AwWebContentsObserver gets re-attached from the original popup
WebView to the one provided by the client, notifications issued inbetween can be
missed on the Java side. To work around this, we assume that WebViews opened as
popups can never be in "vanilla" state (as they are anyway opened as a result of
navigation).
BUG=458569, 462213
TBR=davidben@chromium.org,tedchoc@chromium.org
Bug: 19325392
Change-Id: I3df0484f00d2b816cb0293bec432b2fa6ac5e05b
|
|
avoid memory leak"
Original description (https://codereview.chromium.org/969353004/)
[Android] Cache function templates in GinJavaBridgeObject to avoid memory leak
V8 caches all function templates internally for the lifetime of a web page in an
unbounded cache. Thus, creating a new function template for each call to a
method of injected object caused JS heap memory to grow linearly.
This is similar to a fix for Pepper Plugin objects (https://codereview.chromium.org/785213002/)
BUG=462664
Bug: 19578263
Change-Id: Ie259ceab8625e9e80670b9084aa3cd5813330648
|
|
This reverts commit b9ef84152bce335b4814175204744ea2d5b148b4, which
introduced a new issue with certain software IMEs in fields with
autocomplete="off". The accent issue is a longstanding bug and previous
WebView releases already contained it, so reverting this change does not
introduce a regression.
Bug: 19363073
|
|
This was not the cause of the bug. We have a real fix coming later.
This reverts commit 4922e3cfc859d5fba6b3f212be6623ab51594541.
Bug: 19363073
Change-Id: I1438e8d9107f1f3a2c7ff0cba9ebbc5a3db506ba
|
|
Reason for revert:
Probably the cause of a bug where characters are not properly deleted when
using a Samsung keyboard.
Original issue's description:
> [Clank IME] Make keyCode detection sensitive to autocomplete=on|off.
>
> Fixing Stable blocker for Clank IME.
>
> The old keyCode detection heuristics would emit KEYCODE_DEL when the last
> character of composition is deleted by backspace. This causes the bug where
> the composition gets reset (Japanese keyboard). We fix the the problem by
> emitting keyCode 229 when composition is updated, if autocomplete=on. If
> autocomplete=off then we can can emit the keyCode, provided that we have
> single-character commits. Due to unfortunate collision with
> https://codereview.chromium.org/834133004 , we have to to define constant
> textInputFlagAutocompleteOff for compatibility with trunk and Beta.
>
> The companion WebKit CL is https://codereview.chromium.org/797243003/
>
> BUG=422685
> Committed: https://crrev.com/1a8a145d5ea8289f1e527c3de95f233e4a659cde
> Cr-Commit-Position: refs/heads/master@{#311245}
Bug: 19363073
Change-Id: I25a945f797ffdb5959fd277ad8f86f149d79f8c1
|
|
|
|
Chromium's submodules and repo are fighting. Make them agree.
Change-Id: I4647b0ac7cb0a0496ed494e7b944c51d96f0ef18
|
|
Revert back to using a hardcoded version number instead of the real
version number.
Bug: 19473740
Change-Id: I7f844b02909cb605fcddfceba787c40d71c60d93
|
|
Due bugs in some drivers, sharing GL_LUMINANCE fails and causes causes a
NPE crash. WebRTC is the only feature using GL_LUMINANCE textures which
do not require to be shared, so skip them altogether.
Forking because situation in trunk has changed significantly and this is
no longer appropriate.
BUG: 19366032
Change-Id: I09c076068e1f38daa344009ca7b12cf30ead6df1
|
|
|
|
By not detaching the GL functor until after the teardown, we ran the
risk of stray draw calls occurring that could potentially reinitialize
the hardware renderer, causing the SharedRendererState destructor to
DCHECK.
BUG=
Review URL: https://codereview.chromium.org/920083002
Cr-Commit-Position: refs/heads/master@{#316222}
Bug: 19370054
Change-Id: I38061e7e690a9738e7296f6ad2948caceb3af7e9
|
|
(From https://codereview.chromium.org/411313002/ by h.joshi@samsung.com:
Colored Emoji not drawn in Chrome if font style is set as Bold.
When Bold font is asked, then Skia try to generate image/bitmap from
path (if Bold font is not present) which is not correct case for Colored
Emoji bitmap font.)
Define SK_USE_FREETYPE_EMBOLDEN to prefer FreeType's emboldeing
algorithm to Skia's.
BUG=397069
R=h.joshi
TBR=bungeman
Review URL: https://codereview.chromium.org/800133008
Cr-Commit-Position: refs/heads/master@{#310662}
Bug: 19346255
Change-Id: If83ba41f203f4acdb9021bff32c351e86d4afa2d
|
|
This is a clean Cherrypick of 2 CLs from chromium:
https://codereview.chromium.org/920623002
And https://codereview.chromium.org/922883002/
Original description:
Don't send extra text changed AX events on Android
This fix is small and safe, for merging. The reason this
was happening has to do with contenteditable support
and I'll follow up with a cleaner fix once this is merged.
BUG:19294187
Change-Id: Ifd0de22fdad20a917ca74174c90fce8bec7d87ad
|
|
When exiting fullscreen video playback should continue in
embedded mode. This patch fixes a regression introduced in
M40 by reverting to the M39 state:
https://codereview.chromium.org/618013003/patch/350001/360003
The fix landed in master does not longer applied because
master and M40 have diverged substantially. In master,
this issue has been fixed by moving the responsibility of
destroying the ContentVideoView to the content/ layer here:
https://codereview.chromium.org/845193005/
BUG:19346330
TESTED: I have manually verified this change by building
the WebView and checking that the issue does not longer repro.
Change-Id: I7297c626c355e13b559d15c403db60cca817556f
|
|
crrev.com/8cd9cd17b1b52ef751a5a101189394891d73f351
BUG:19047869
Change-Id: Ibb25040a8b66a7c69f162ada10f9e1563bcd22f1
|
|
Disable NOTIMPLEMENTED() as the messages generated are not actionable by
app developers.
Bug: 15303655
Change-Id: I8d52c69874fe2818ac58235d9441936798dc60d6
(cherry picked from commit bf063fe8d7408cd65ec84b146e4254baa2aa7055)
|
|
scheme."
Fixes a crash in apps using
WebSettings.setAllowUniversalAccessFromFileURLs(true).
> BUG=449075
> TEST=content_unittests --gtest_filter=NavigationControllerTest.IsInPageNavigation
>
> Review URL: https://codereview.chromium.org/855883002
>
> Cr-Commit-Position: refs/heads/master@{#313051}
Change-Id: I7360997ae6eec0279c932be555bfcb097e2804a7
|
|
This commit was generated by merge_to_master.py.
Change-Id: Ibdab6876b11f066ecec5190933d7ef70850ef51a
|
|
This commit was generated by merge_to_master.py.
Change-Id: I9fa45d741f6e055e37326e1f41d6e11e0c97bac4
|
|
This is a cherry pick from chromium:
https://crrev.com/86fca587a88a12c485c5b3bfaf7d3029561137af
Original CL description:
The current crash handler prints a message on logcat of the form
"### WebView crash. Version ..." whenever a crash is detected in an
Android app which happens to have a WebView.
Due to the in-process nature of the WebView, the crash handler is
triggered regardless of the actual cause of the crash, which might be
totally unrelated with the WebView or the chromium codebase at all.
The current wording is misleading as it erroneously suggests that the
crash is always due to the WebView.
BUG: 19293339
Change-Id: Ieeba42f19f7309fcbda5fa6ca0baa1cb33955092
|
|
into m40
|
|
This commit was generated by merge_to_master.py.
Change-Id: Ieae58fdd7ffd751ca0120c6f8222338971969f68
|
|
This commit was generated by merge_to_master.py.
Change-Id: I06201d7079ec55ca5d66023f88ce8a2ece317095
|
|
This is a cherry pick from chromium:
https://crrev.com/9178c77a0167ee7c73364b21a6f3a633029b7a44
Original CL description:
PictureLayerImpls in a tree should continue using the same viewport rect
for tile priority until UpdateTiles() is called with the new value of
viewport rect for tile priority. Otherwise, a PictureLayerImpl could be
in an inconsistent state that could lead to a wrong decision about
AllTilesRequiredForActivationAreReadyToDraw.
This CL caches the viewport rect for tile priority in PictureLayerImpl.
Conflicts:
cc/layers/picture_layer_impl.h
BUG: 18915361
Change-Id: I7738cf793484fa46670388e0cf0e1d2cefbbddd4
|
|
This commit was generated by merge_to_master.py.
Change-Id: I5161a6d3eb93b632c6e3cf3887d0b03eb3a59bd2
|
|
This commit was generated by merge_to_master.py.
Change-Id: Ie5cbec1748e252af0bfed0f0172022bd46c3178c
|
|
This commit was generated by merge_to_master.py.
Change-Id: I01bbd0eb75057d0f3be881ab85a6ed78b6db8957
|
|
This commit was generated by merge_to_master.py.
Change-Id: I327855d5ff2f6fff543271e71e90eb43d72bb003
|
|
This commit was generated by merge_to_master.py.
Change-Id: I17568cc6fef7aca9b56cba2b193feacc604444ba
|
|
This commit was generated by merge_to_master.py.
Change-Id: I54c57fa699c7bcf214338db5ed42fa3b347c3d40
|
|
|
|
Change-Id: Ic99f9c4291fc5b1f74ccec02f49842cf78562e6f
|
|
This commit was generated by merge_to_master.py.
Change-Id: I133d9df2c75ea608f1bcd57c6705ee329e7d742e
|
|
This commit was generated by merge_to_master.py.
Change-Id: I4eeba491372f6b0901770671a77a6cde0232344c
|