| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
issue: 4982074
Change-Id: I5d86539a17393f3060cd67bd4c6888734037c7e4
|
|
|
|
|
|
|
|
| |
This reverts some of my previous change which wrongly treats
format-detection as a viewport change.
issue: 4975315
Change-Id: Icb3ab9b813010b253a59fca6992deb1aa4d186e7
|
|
|
|
|
|
|
|
|
| |
The Android's customized way of parsing viewport meta tags is kept intact;
while the viewport update notification mechanism is changed to use webkit's
way. This gives much better notification of viewport switching.
issue: 4975315
Change-Id: I7896b67d684efec015245ee804a9243e72ff0b50
|
|
|
|
| |
Change-Id: I5cf0e2da4d4f48be5daf176b5aac8222b9919ba9
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the existing code we created a sharedBitmap for BaseTiles and
never used it instead opting for createing bitmaps on the stack to
enable partial invalidation. This CL removes the sharedBitmap concept
and instead creates all bitmaps on the stack.
This means that BackedDoubleBufferedTexture no longer needs to have
a bitmap member, but instead simply takes the bitmap from the caller
and uploads it to the appropriate texture. To make this upload clean
we now pass the bitmap via const references instead of pointers.
Change-Id: Ie218c4b4564e5574ca6e404d4857904ab41a3a5c
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| | |
Otherwise, there will be GPU memory leak.
bug:4947376
Change-Id: Ib76a47c197d7c1a01471c4b38e210e0d5dd9fa02
|
|/
|
|
| |
Change-Id: I1dc4622e0ce1602f6dc314f0b510c41adb95a443
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
B/c of driver limitation, we are using 2D texture target for our Surface
Texture, this will be switched to EXTERNAL_OES soon. In order to have smooth
transition, I added the code which can handle both types and it depends on what
Surface Texture itself reports.
Tested with both modes on Crespo since its driver support both.
bug:4905428
Change-Id: Ic91702e7b8f75329f7d948e9217f7fc689a95bbb
|
|/
|
|
|
|
|
|
|
| |
Instead of using border which may be too broad, using whether an object
is floating to fix flickr's reflow issue. Checked sites like slashdot.org
and nytimes.com, this works better.
issue: 4596265
Change-Id: Ic263b1e6fddedb47e410687ed04cd2ac7ccb7bed
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This also fixes the case where flickr header's position
is not good since it's reflowed for issue 4596265.
issue: 4596265
Change-Id: I8445ec408a813935871c5d011b23b70e569105d3
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: 4743033
Change-Id: Ic0603ecf3af9290bd6d374aa8ddf4342948064ac
|
| |/
|/|
| |
| | |
Change-Id: Iad5ef9dc1f9944a326e45dd2721cb0005e69f425
|
|/
|
|
| |
Change-Id: Ie88de19e89e298b69b106fbb42d2b9d26bb98014
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I1a9d8eab3e5259eade94fc9e825ec4d162a1e392
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes slashdot.org after recent webkit merge, since the removed code
will sometimes require extra layout.
This code is two years old, and related to iframe flattening, which
is not used any more in Android. Android still does frameset flattening.
Verified sites such as developer.android.com are still working.
issue: 4753055
Change-Id: I69f78bec53671eb488b629bde7cc2c3158f1a510
|
| |
| |
| |
| | |
Change-Id: Ibee33c53d65a6c1b98f5e88ed79862cd30418347
|
| |
| |
| |
| |
| | |
bug:4406718
Change-Id: Iea532c639bf41aad2488819d42c315a0e3d747fd
|
|/
|
|
| |
Change-Id: Ide38fce4ba0be0eb506cb4c5497915e11812b6bd
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I852c546b2c62419ccfb96ed1c0d157e49a3b1aef
|
|\ \
| |/ |
|
| |
| |
| |
| | |
Change-Id: I0d43dd94a1bb4666d20a39b2b272337e89a21d8b
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Apply WebKit change http://trac.webkit.org/changeset/83002 to
our GraphicsContext port.
Bug: 4674341
Change-Id: I1399ae0f12aff3f24417a7d6f36006a73e8e48ff
|
|/
|
|
|
|
|
|
|
|
|
|
| |
We used to rely on the fact that RenderLayerBacking is the only subclass of
GraphicsLayerClient, but now the RenderLayerCompositor also inherit it and
is used for iframe. That cause us to get invalid pointer in GraphicsLayerAndroid.
The solution here is to disable the new webkit approach b/c we have our own
iframe support already.
bug:4592195
Change-Id: Ia786233907d83028fdc6865c28fbbd5291564ad0
|
|
|
|
| |
Change-Id: I959b25a9447154395f168132f908c0f4512d4be6
|
|
|
|
|
| |
Bug: 4442995
Change-Id: I9c37d7022946fd66e1ee635328182bf1456b0de7
|
|
|
|
|
|
|
| |
See http://trac.webkit.org/changeset/85873
Bug: 4442995
Change-Id: I27c5d678a534ec0b64d59868f6f77e51c477e89d
|
|
|
|
| |
Change-Id: I0501b484b9528e31b0026e5ad64416dd6541cdde
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch moves many defines from WebCore/config.h to keep
all of the Android defines together.
Also, WebCore/config.h should not be used by JavaScriptCore
(though currently it is on Android), whereas wtf/Platform.h
is always included.
Some Android defines in WebCore/config.h are already usptreamed,
but will be removed in https://bugs.webkit.org/show_bug.cgi?id=62602
Change-Id: Ic6d8c45f4f846a2a7a2d9766179302526c10e2af
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Bug: 4486008
Change-Id: Iaf810878c6ed216e2431a7718de899a9e8e0d6f8
|
| |
| |
| |
| |
| |
| | |
Cherry pick of upstream patch http://trac.webkit.org/changeset/87424
Change-Id: I6546831e7cecf11bbfd194f0620c56f293b56f2d
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Shadow DOM work needs to be applied to our local edits to make
SliderThumb work with touch events.
Several upstream changes are relevant...
http://trac.webkit.org/changeset/83256
http://trac.webkit.org/changeset/83397
http://trac.webkit.org/changeset/83545
http://trac.webkit.org/changeset/84222
Change-Id: Ie653c87e6e1d823c50ee22c406aaa79a22bcf530
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The JavaInstance class is now an interface, so use the
provided JavaInstanceJobject implementation instead.
See http://trac.webkit.org/changeset/82950
Change-Id: I782e3887e4f059733fbc054ca1d9d97d94e817ef
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
iframe compositing propogation now works for <object> and framesets so
the methods have been renamed - implement that renaming in our code.
See http://trac.webkit.org/changeset/83518
Change-Id: Id1fd6d47f5ac4546f6eddf443658b4b481542292
|
| |
| |
| |
| |
| |
| |
| |
| | |
GraphicsContext::roundToDevicePixels has a new parameter.
See http://trac.webkit.org/changeset/83216
Change-Id: I9f215b450c790ac1e6a54959e5cbee43d3a25694
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Need to include the Android ImageBufferData header. To avoid recursive
includes, rename android/ImageBufferData.h to
android/ImageBufferDataAndroid.h
See http://trac.webkit.org/changeset/83786
Change-Id: Ica2d0c5350810b918d034d0ac227eb6255939584
|
| |
| |
| |
| |
| |
| |
| | |
See http://trac.webkit.org/changeset/82562 for
new XMLTreeViewer generation.
Change-Id: I52c8d510602e7e77ea6a134510f8e5bb6b0c4d9a
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Platform.h
ENABLE_FULLSCREEN_API (http://trac.webkit.org/changeset/83997)
WTF_USE_SKIA (http://trac.webkit.org/changeset/84106)
JSNavigatorCustom.cpp
V8NavigatorCustom.cpp
ENABLE(APPLICATION_INSTALLED) (http://trac.webkit.org/changeset/83287)
CSSStyleSelector.cpp
ANDROID_CSS_RING (http://trac.webkit.org/changeset/83986)
Document.cpp
ANDROID_META_SUPPORT (http://trac.webkit.org/changeset/83349)
ANDROID_INSTRUMENT (http://trac.webkit.org/changeset/82992)
HTMLInputElement.cpp
ANDROID_ACCEPT_CHANGES_TO_FOCUSED_TEXTFIELDS (http://trac.webkit.org/changeset/82534)
RangeInputType.cpp
ENABLE(TOUCH_EVENTS) (http://trac.webkit.org/changeset/83256/)
ChromeClient.h
ANDROID_INSTALLABLE_WEB_APPS (http://trac.webkit.org/changeset/83375)
EventHandler.cpp
PLATFORM(ANDROID) (http://trac.webkit.org/changeset/83522)
Settings
ANDROID_PLUGINS (http://trac.webkit.org/changeset/83201)
ANDROID_BLOCK_NETWORK_IMAGE (http://trac.webkit.org/changeset/83628)
Gradient.cpp
Graphicscontext.cpp
HTMLCanvasElement.cpp
USE(SKIA) && !PLATFORM(ANDROID) (http://trac.webkit.org/changeset/84088)
USE(SKIA) && !PLATFORM(ANDROID) (http://trac.webkit.org/changeset/84101)
PluginView.h
ANDROID_PLUGINS (http://trac.webkit.org/changeset/84071)
RenderBox.h
ANDROID_LAYOUT (http://trac.webkit.org/changeset/82611)
RenderIframe.cpp (moved code to RenderPart.cpp)
PLATFORM(ANDROID) (http://trac.webkit.org/changeset/83518)
RenderLayer.cpp
ANDROID_OVERFLOW_SCROLL (http://trac.webkit.org/changeset/83899)
RenderLayer.h
RenderLayerBacking.cpp
ANDROID_OVERFLOW_SCROLL (http://trac.webkit.org/changeset/83820)
Change-Id: Ieabe98f4e01610b6a73e961b673e2fa99b0010e7
|
| |
| |
| |
| | |
Change-Id: Ic1a909300ecc0a13ddc6b4e784371d2ac6e3d59b
|
| |
| |
| |
| |
| |
| | |
JavaTypeString is only available for V8.
Change-Id: I53a1d36b61268496486264cbc6c96fe1e0a5fbd3
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This was introduced by the latest merge to WebKit r82507. WebKit now
uses a new JavaTypeString, distinct from JavaTypeObject, for
representing strings in the JNI bridge. We need to account for this
when building the JNI method signature.
See https://bugs.webkit.org/show_bug.cgi?id=62389 for details.
Bug: 4585284
Change-Id: I6a54679b954c32bf03d715da3c958c61baa5fecc
|
|\ \ |
|