| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
nothing was defined
Change-Id: Ib9f5b473cbda0518e332332cdc1c515652150a8c
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Gifs use a different decoding mechanism from other images. The
default webkit implementation allocates a bitmap for the gif,
which is serialized when the picture is flattened. A page with
a 25K display list may flatten into a 20M file if GIFs are
included as bitmaps.
GIFs can be written like other image types, as streams; then
the display list flattens to a 140K file. Currently, the
Skia-based images only can handle non-animated types.
When animated gifs was recently enabled, the flattened file
size grew. All gifs were treated as if they could be animated,
and all were decoded into bitmaps with straight memory allocations.
This change uses the stream-allocation mechanism if the GIF
has only one frame, and is therefore not animating.
Change-Id: Ie2360bb6f20515b81bd62761ca97242f33ffb43b
http://b/2650945
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a new layout test and triggers a crash inside screenRect() by
accessing the null page pointer. Other platform implementations perform
a null check on page in this function, so we now do the same to prevent
the crash.
Change-Id: I2403d7adc157daae69f6fb53bbbf212d9d04341c
|
|\ \
| | |
| | |
| | | |
parsing the meta-tag"
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
meta-tag
The Android meta-tag parsing code was originally copied from the iPhone
implementation. A later change added the semi-colon to the list of separator
characters, motivated by Reader. See http://b/issue?id=1416841 and
https://mondrian.corp.google.com/changelist/115656-p9
Meta-tag support has since been added to WebKit in
http://trac.webkit.org/changeset/57775. The upstream parsing code does not
consider the semi-colon to be a separator. The upstream parsing code was merged
into Android as part of the merge to WebKit r58033 in
https://android-git.corp.google.com/g/#change,50648
This change removes the Android-specific changes so the semi-colon is no longer
considered a separator. This brings Android back into line with iPhone and other
browsers.
Change-Id: Id4cbbadb414d0508a89006d9beb91c56fa1f8daf
|
|\ \
| | |
| | |
| | | |
the list for JSC"
|
| |/
| |
| |
| |
| |
| | |
for JSC
Change-Id: I142c9198785dd18ac9b727a42564b27036548958
|
|\ \
| | |
| | |
| | | |
writeToFile()"
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The Android version of writeToFile() tries to support interrupted writes, but
has a bug as the data pointer is not updated. So instead we take the standard
POSIX version.
See https://mondrian.corp.google.com/changelist/75998-p9
and https://bugs.webkit.org/show_bug.cgi?id=38908
Change-Id: I011671211017005a06727e436f92e8458902a7db
|
|/
|
|
| |
Change-Id: I6545eab16de0c3355b188ffc643eec1f992877a2
|
|
|
|
|
|
|
|
| |
missing PassRefPtr.h include
See http://trac.webkit.org/changeset/58826
Change-Id: I00a2682dc0e9d9ca6cc9f3363b9f170075dd7817
|
|
|
|
|
|
|
|
| |
jni_jsobject.h for jlong_to_pt() and ptr_to_jlong()
See http://trac.webkit.org/changeset/58775
Change-Id: Id1efa09e2f3578f8c782da0686c2df4d87fc83c3
|
|
|
|
|
|
|
|
| |
conflicts with FileSystemPOSIX.cpp
See http://trac.webkit.org/changeset/58774
Change-Id: I646d82752feaafaf0ece6e1cdd099ae2a200995e
|
|
|
|
|
|
|
|
| |
Geolocation::suspend()/resume() back in
See http://trac.webkit.org/changeset/58061
Change-Id: Ie7b4b4891391656a6cc25cd30b3913f0638a0302
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ScriptDebugServer::topStackFrame() on Android
ScriptDebugServer is guarded with (JAVASCRIPT_DEBUGGER), which is not defined on
Android. An attempt was made in https://bugs.webkit.org/show_bug.cgi?id=38531 to
move ScriptDebugServer::topStackFrame() to ScriptCallStack to avoid the linker
error. However, this causes crashes on Android as our version of the V8 snapshot
is not consistent with this.
This fix is a temporary work-around to avoid the problem by simply not calling
ScriptDebugServer::topStackFrame(). The problem will be fixed properly upstream
when this code is refactored, as described in the WebKit bug.
Change-Id: I3952eed2e56dbb5a6f6204276bd499e79bba2227
|
|
|
|
|
|
|
|
|
|
|
| |
AccessibilityObject::getAttribute
This is used in RenderMenuList. Neither implementation nor call site are guarded
with HAVE(ACCESSIBILITY) but Android does not compile any accessibility code.
See http://trac.webkit.org/changeset/55425
Change-Id: I3e94a80052287d38c6266e4f01b1b31b127e7781
|
|
|
|
|
|
|
|
|
| |
Some V8 bindings files have been removed now that more of the bindings are
auto-generated. Android has some modifications due to the addition of
navigator.connection, which causes conflicts. However, we can safely delete
these files.
Change-Id: I7188894a3d1dbe380eae7e2cc18409836ce8cafc
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RenderIFrame.cpp
The Android iframe-flattening code was in RenderPartObject. The rendering
classes have been refactored upstream in http://trac.webkit.org/changeset/57866
so that most of RenderPartObject was moved to RenderIFrame. RenderPartObject was
then removed in http://trac.webkit.org/changeset/57900.
Iframe-flattening was also added upstream in
http://trac.webkit.org/changeset/56718.
This change takes the Android iframe-flattening code from RenderPartObject and
moves it to RenderIFrame. It also renames FLATTEN_IFRAME to
ANDROID_FLATTEN_IFRAME and FLATTEN_FRAMESET to ANDROID_FLATTEN_FRAMESET for
clarity.
Change-Id: I1af8d042f8d0c4abd513f8a315ac681360c1cc53
|
|
|
|
|
|
|
| |
This file has been deleted upstream now that more V8 bindings are
auto-generated, but we have local modifications, so we must keep these parts.
Change-Id: I0d1497bf3f54f977ef4753800b127a32f38a30ea
|
|
|
|
|
|
| |
See http://trac.webkit.org/changeset/56337 and http://trac.webkit.org/changeset/57095
Change-Id: I79098600dd15de6c4d699bb75bbbc7dcb6b87754
|
|
|
|
|
|
|
|
| |
platformStaticGetValue()
See http://trac.webkit.org/changeset/55432
Change-Id: I21b1185ce5a86d902c7a5de3f7866e82c6fe3ee8
|
|
|
|
|
|
| |
See http://trac.webkit.org/changeset/56825
Change-Id: I8ba6a9685dcd1d8c4dec3400fba81e19fcbfe74d
|
|
|
|
|
|
| |
See http://trac.webkit.org/changeset/57738
Change-Id: I1d10e7858488f40013bffa3e8f8339db7fff7de0
|
|
|
|
|
|
|
| |
This was added to WebKit in http://trac.webkit.org/changeset/55433. It does not
cause problems on Chromium as they exclude this file from the build.
Change-Id: I77e94d5c18d99fb24578416ef31e559f35386372
|
|
|
|
|
|
| |
See http://trac.webkit.org/changeset/55688
Change-Id: I03ecd486149d48a36f65222c9ac8cc1a957306c0
|
|
|
|
|
|
| |
See http://trac.webkit.org/changeset/57215
Change-Id: I441f2905fe3882d3da2f4e9c8084a7d09d94b6f6
|
|
|
|
|
|
| |
See http://trac.webkit.org/changeset/57775
Change-Id: I2ab1caa2a90e4583afbf6a07ed68bdb360e9fb15
|
|
|
|
| |
Change-Id: Ie97b3c249bbda11ec4bc249be915f88361858d85
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- CanvasRenderingContext2D.cpp - Take upstream, conflict due to cherry-pick of security fix, see 285b474734e82bc42b25e48ea4824f8050badb4f
- CanvasSurface.cpp, HTMLCanvasElement.cpp - convertLogicalToDevice has been refactored. See http://trac.webkit.org/changeset/56447
- Chrome.cpp/h, ChromeClient.h - Take upstream, conflict due to cherry-pick of cancelling Geolocation permission request
- Document.h - Take both, conflicts due to ANDROID_META_SUPPORT
- DragImage.h - Take both, conflict due to Android addition
- EmptyClients.h - Take upstream, conflicts due to Geo cancel permission request
- EventHandler.cpp - Take both, conflicts due to recently upstreamed touch events and ANDROID_PLUGINS
- EventHandler.cpp - Keep ours, conflict due to touch event bug fixes not yet upstreamed. See 7f034a1734d634dd1fdb3b64817d5828b5e46922 and 73adc26dba4be1d9da34a7f0907cb7b12f10c909
- FileSystemPOSIX - Take both, conflict due to ANDROID_PLUGINS
- FrameLoader.cpp - Take both, conflct due to ANDROID_BLOCK_NETWORK_IMAGE
- FrameView.cpp - Take both, conflict due to Android frame flattening
- Geolocation.h - Merge conflicts due to Android-specific changes
- Geolocation.cpp - Take upstream, conflict due to addition of Geolocation maximumAge
- GeolocationPositionCache.cpp - Take upstream, conflict due to addition of ENABLE_GEOLOCATION guards
- Gradient.h - Take both, conflict due to Android addition
- HTMLLinkElement.cpp, DocLoader.cpp - Take both, conflict due to new link prefetching not yet upstreamed. See f91ac8eab3399adb5325701bebe0590a77e49df7
- HTMLMetaElement.cpp - Take both, conflict due to recently upstreamed meta element
- JavaInstanceJSC.cpp - Take both, conflict due to Android additional logging
- MediaPlayer.cpp/h - Take both, conflict due to Android-specific change
- PlatformTouchPoint.h - Take upstream, conflict due to recently upstreamed unsigned stuff
- RenderFrame.cpp, RenderFrameSet.h - Take both, conflict due to Android frameset flattening
- RenderLayerCompositor.cpp - Take both, conflicts due to Android layers code
- Settings.cpp/h - Conflict due to ANDROID_PLUGINS
- TextInputController.h - Take upstream, git got confused
- V8DOMWindowShell.cpp - Take upstream, conflict due to cherry-pick of method to add V8 bindings for page cache, see 8fecd9c9a62aa89fb44ed3142ba583dc7b8cbe29
- V8DOMWraper.cpp - Take upstream, conflict due to recently upstreamed WORKERS guards
- WebCore.xcodeproj - Take upstream, conflict due to addition of Geolocation maximumAge
- Widget.h - Take both, conflict due to Android addition
- jsc/JNIUtilityPrivate.cpp - Take upstream, conflict due to switching from bzero to memset
- mac/WebCoreSupport/WebChromeCient.h - Take upstream, conflicts due to Geo cancel permission request
Change-Id: I1b75eac220faddf2f84c7fd4fd3436a5e07edf64
|
|
|
|
| |
Change-Id: If006c38561af287c50cd578d251629b51e4d8cd1
|
|
|
|
|
|
|
|
| |
This file is not needed and causes problems with the latest version of the V8 code generator.
It was removed from the Chromium build in http://trac.webkit.org/changeset/49309
Change-Id: I6966683e51479dc171ff7d271cc962e7ae059946
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
The compilation issue happens when android webcore instrumentation is turned on.
issue: 2582105
Change-Id: I403b43c69a0561ee52baf4265831dca185264ced
|
|/
|
|
|
|
| |
https://android-git.corp.google.com/g/#change,41406
Change-Id: Ief37a7d9879308f0749fcd569e82fddc3f989a8a
|
|
|
|
|
|
| |
These will be required with the upcoming WebKit merge.
Change-Id: I610d6bf5ea919c6842808fd6090f68dc010f4b2e
|
|\
| |
| |
| | |
handling. The RefPtr returned from m_originatingTouchPointTargets.take() was only in scope for the duration of the else block but we saved the raw pointer it wrapped. When the else block ende
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
returned from m_originatingTouchPointTargets.take() was only in scope for the duration of the else block but we saved the raw pointer it wrapped. When the else block ended, the RefPtr destroyed it
Merge commit '7f034a1734d634dd1fdb3b64817d5828b5e46922' into froyo-plus-aosp
* commit '7f034a1734d634dd1fdb3b64817d5828b5e46922':
Fix a ref counting bug in touch event handling. The RefPtr returned from m_originatingTouchPointTargets.take() was only in scope
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
m_originatingTouchPointTargets.take() was only in scope
for the duration of the else block but we saved the raw pointer it wrapped. When the else block ended, the RefPtr destroyed itself, also
deleting it's enclosed pointer if it held the final ref. But we had a saved copy of this raw pointer and then went on to use
it later.
Fix bug 2543728.
Change-Id: I90e17693e15bff0969f103b5947d004837189c44
|
|\ \ \
| |/ /
| | |
| | | |
from a page with your finger still down (when the old and new pages have touch event handlers installed) and then releasing your finger on the new page after WebCore has performed a garbage c
|
| |\ \
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
finger still down (when the old and new pages have touch event handlers installed) and then releasing your finger on the new page after WebCore has performed a garbage collection.
Merge commit 'da713c0266664dc15b021e99cca31cadc5bd2bdc' into froyo-plus-aosp
* commit 'da713c0266664dc15b021e99cca31cadc5bd2bdc':
Fix a crash caused by navigating away from a page with your finger still down (when the old and new pages have
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
down (when the old and new pages have
touch event handlers installed) and then releasing your finger on the new page after WebCore has performed a
garbage collection.
Cherry pick of webkit.org revision 58760.
Bug=2543728
Change-Id: I4c9a896ff81881211746451f49158b7e99eb9166
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Compiled successfully for both V8 and JSC.
The libwebcore size changes from 5354080 to 6072344, the diff is 700KB.
Change-Id: Id95abd8b8f2181ed7789a95e0675cb8436e11bf7
|
|/ / /
| | |
| | |
| | | |
http://b/issue?id=2268353
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Ie9ba4c69,I35363367,I18aaae5f,I2c315360,I4f163c97,Ib640e64c,I98a4af82
* changes:
Merge webkit.org at r55033 : Update WebKit revision
Merge webkit.org at r55033 : Update Android-specific LayoutTest expected result
Merge webkit.org at r55033 : Implement FrameLoaderClient::didTransferChildFrameToNewDocument for Android
Merge webkit.org at r55033 : Implement PluginPackage::NPVersion for Android
Merge webkit.org at r55033 : Implement new ChromeClient::iconForFiles method for Android
Merge webkit.org at r55033 : Fix merge conflicts
Merge webkit.org at r55033 : Initial merge by git
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
See http://trac.webkit.org/changeset/54940
Change-Id: I2c3153606ab0eb9a4598e211def2f07f60eab3da
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Android.v8bindings.mk - Keep ours, conflict due to upstreaming of using DerivedSourcesAllInOne.cpp
- V8Index.h - Keep ours, conflict due to upstreaming of touch events
- GeolocationService.h - Take both, conflict due to Android-specific change for pausing service
- PluginView.cpp - Take both, conflict due to Android-specific change to guard JSC headers
- V8DOMWrapper.cpp - Keep ours, conflict due to addition of WORKERS guards
Change-Id: Ib640e64caecbb8cb31272dbfbc18d95f32f9d126
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: I98a4af828067cc243ec3dc5e5826154dd88074b5
|