| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: If006c38561af287c50cd578d251629b51e4d8cd1
|
|
|
|
|
|
|
|
|
|
| |
- 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
|
|
|
|
|
|
| |
Fix bug: 2588887
Change-Id: I06d64e58a95d9dd8d7e4308e1601c55d6d33663f
|
|
|
|
|
|
|
|
| |
Check the frame's context at PageCache save and restore time to avoid crashing when it's null.
Fix bug: 2564844
Change-Id: Ifef3fcf271b1366d4f63c42da1a9ac08bb8b78ed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
createScriptInstanceForWidget(widget) is called,
we need to release the reference of the matching
npObject to avoid leak.
HTMLPlugInElement::getInstance() only calls
createScriptInstanceForWidget(widget) once. But
HTMLEmbedElement is using its closest ancestor who
has objectTag to get the widget. So the same widget
can exist in the HashMap if both <object> and its
child <embed>'s getInstance() are called.
Fix http://b/issue?id=2553266
|
|
|
|
|
|
|
|
| |
which adds V8 bindings for page cache.
Fix b: 2533219
Change-Id: I57f067adbbef76b4f8ec6c50b9e85fb2b7fc619a
|
|
|
|
| |
Change-Id: Icffc7b0d5f9a9b2da66dca37c0c8d084c11491b7
|
|
|
|
|
|
|
|
|
|
|
|
| |
The motivation for this change is to allow us to disable workers on Android,
because V8 on Android does not have the required locking.
This change will not be upstreamed because the code has been refactored in
tip-of-tree WebKit.
See http://trac.webkit.org/changeset/55096
Change-Id: I23ce1e5aecc2897da240b5229585b8e6617d8ebf
|
|
|
|
|
|
|
|
|
| |
The motivation for this change is to allow us to disable workers on Android,
because V8 on Android does not have the required locking.
See http://trac.webkit.org/changeset/56112
Change-Id: Ieee214f4765af3188bbdc51c56f14883f6a6779c
|
|
|
|
|
|
|
|
|
|
|
| |
globalObjectPrototypeIsDOMWindow
The motivation for this change is to allow us to disable workers on Android,
because V8 on Android does not have the required locking.
See http://trac.webkit.org/changeset/55084
Change-Id: If72cb478fb7dad6be44eaa2c1ca19e9790a9dda0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
wrapping in V8 bindings
The motivation for this change is to disable workers on Android, because V8 on
Android does not have the required locking.
The current version of WebKit in Android (54731) uses workers features without
ENABLE(WORKERS) guards in the V8 bindings. In particular,
V8DOMWrapper::instantiateV8ObjectInWorkerContext is used from generated code
without guards.
Fixing the code generator would be difficult and would be wasted effort as
V8DOMWrapper::instantiateV8ObjectInWorkerContext no longer exists in tip-of-tree
WebKit. Instead, we cherry-pick the WebKit change which removes this method.
See http://trac.webkit.org/changeset/54972
Change-Id: Ie6365073d7a4d92aa7c1553d87a7e1c1ed514118
|
|
|
|
|
|
|
|
| |
inside forgetV8ObjectForNPObject is causing a double deletion."
Right problem, wrong fix.
This reverts commit 9e0d526d0170e26b1dc2d0da8347cca28b5f3507.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
forgetV8ObjectForNPObject is causing a double deletion.
In ScriptController::clearScriptObjects, we call Unregister (which without this change causes Release to get called in forgetV8ObjectForNpObject).
If the ref count gets to 0, we free the object in Release. Then when Unregister returns, we call Release again in the ScriptController with the
same just-free'd pointer. If we're unlucky, then the Deallocate and free gets called again. We're also trying to access members such as the reference
count and deallocation function through a dead pointer.
Also, in the case where the Flash does not clear it's window object, we call Deallocate directly inside ScriptController::clearScriptObjects. This causes
Unregister to get called (as the object is still alive) which calls Release through forgetV8ObjectForNPObject, which results in a recursive call to Deallocate,
which frees the memory. Then the stack unwinds and we happily try to free again from the first call to Deallocate.
Fix these issues by removing the extra call to NPN_ReleaseObject in forgetV8ObjectForNpObject.
Change-Id: I7f6d21cd4ff38e29bd1a178e4816d023560b6b16
|
| |
|
| |
|
|
|
|
| |
javascript having been initialised.
|
|
|
|
|
|
|
|
| |
values
See http://trac.webkit.org/changeset/55020
Change-Id: I4d6c067dcafc43d2798c55e042e446d4964b326f
|
|
|
|
|
|
| |
This matches Chromium
Change-Id: I386e4e307e16d8b06eaf258a73d78dfdd9645bf8
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
This updates Android to match Chromium
See http://trac.webkit.org/changeset/54957
Change-Id: I41c082460f00e1c0ec32bf180205ca40fd2f190a
|
|\ \
| |/
|/|
| | |
landed to webkit.org in https://bugs.webkit.org/show_bug.cgi?id=35094"
|
| |
| |
| |
| |
| |
| | |
webkit.org in https://bugs.webkit.org/show_bug.cgi?id=35094
Change-Id: Id8bfd38800bf38de704efbad3afe9b8e53367d13
|
|/
|
|
| |
Change-Id: I28ccbf06e6490f6be5e024218ec823dd156d79b2
|
|
|
|
|
|
| |
http://trac.webkit.org.changeset/54950
Change-Id: I7da830fcd1d996a23e3f9ca61fa668a99ad80431
|
|\
| |
| |
| | |
in V8 bindings"
|
| |
| |
| |
| |
| |
| |
| |
| | |
bindings
See http://trac.webkit.org/changeset/54881
Change-Id: I7bf987cbdc8e88e39317551c098475d8f92cd582
|
|/
|
|
|
|
| |
See http://trac.webkit.org/changeset/54880
Change-Id: I5665991bb4f7d3680c00b42194a9208d1daa90f0
|
|\
| |
| |
| | |
on an include in V8DocumentCustom.cpp"
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
include in V8DocumentCustom.cpp
Adding generated headers to the build, even when for disabled features, is preferred to using guards around includes.
See https://bugs.webkit.org/show_bug.cgi?id=34812
Also cleans up some other Android-specific changes in WebCore/bindings/v8.
Change-Id: I37a174bfaef0d659fc3cef08d084af8861b65ac9
|
|\ \
| |/
|/| |
|
| |
| |
| |
| | |
Change-Id: I91cd4224ee4df8de105dca179b42ee1428ab288d
|
| |
| |
| |
| |
| |
| |
| |
| | |
RuntimeEnabledFeatures.cpp
see http://trac.webkit.org/changeset/54593
Change-Id: Iab1af86c65db24849fbdb07cc4b1692133d7ae87
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- AutoFillPopupMenuClient.h - Take theirs, git got confused
- PluginView.h - Conflict due to new OS macro
- Gradient.cpp - Conflict due to new argument due to setPlatformGradientSpaceTransform
- Android.derived.v8bindings.mk - Keep ours
- DragImage.h - Take both
- V8DocumentCustom.cpp - Take theirs
- XCode project - Take both to keep Android-addition of GeolocationPositionCache
Change-Id: I3f294a71af93fb4e02b57e0169bd25143132df15
|
|/
|
|
| |
Change-Id: Ia79977b6cf3b0b00c06ef39419989b28e57e4f4a
|
|
|
|
|
|
|
|
| |
headers to V8 generated code.
See http://trac.webkit.org/changeset/54658
Change-Id: If52c6dc9b2c09d4ae028d913da653c2373eb151b
|
|
|
|
|
|
|
|
| |
guards for V8
See http://trac.webkit.org/changeset/54650
Change-Id: Ieda3be45b1979c0f9d776cf6b7639f0e67f1466f
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Take both for Android makefiles, other than typo for JavaNPObjectV8 upstream
- Take theirs for XCode project file and ChangeLog
- Fix trivial header conflict in V8DocumentCustom
- Keep ours for fix in JNIUtilityPrivate.cpp
- Take theirs for V8DOMWrapper.cpp. Conflict is due to Android addition of TouchEvents, which conflicts with http://trac.webkit.org/changeset/54259
- Take both for Android addition of applicationInstalledCallback
- Take both for Android JSC JIT changes in Platform.h
Change-Id: Ib1a748f204a07a7e736feeee6a0f30f7453754a7
|
|
|
|
| |
Change-Id: Ib489d2ff91186ea3652522e1d586e54416a2cf44
|
| |
|
|
|
|
|
|
| |
This CL contains the wiring between the API and the Java side.
Fix b: 2371005
|
|
|
|
|
|
| |
This CL contains the JSC DOM bindings.
Fix b: 2371005
|
|
|
|
| |
ece0a38a9778edd2ae7a550df7dcd38d1e11e7d0
|
|\ |
|
| |
| |
| |
| |
| |
| | |
This CL contains the V8 DOM bindings and IDL changes.
Fix b:2371005
|
|/
|
|
|
|
|
|
| |
and line number in V8Proxy, as we now support that.
This requires an external/v8 change, see 39929.
Change-Id: Ie4cab862ebef7ad569b070b11a8bae67e89f2c38
|
|
|
|
|
|
| |
This is achieved by cherry-picking WebKit patch http://trac.webkit.org/changeset/54218
Change-Id: I953939c9ee0a478c26f0481d923595325b67f718
|
|
|
|
|
|
|
|
|
|
|
|
| |
flags
These have been modified to default to true on Android.
We also set the new flags to default to true.
Note that the enabler flag for database has changed.
See http://trac.webkit.org/changeset/53595
Change-Id: I2832c4bcb316f481a33a8c00e7fe90dffa8dcdcf
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
destructor to Visitor class
Android had added a virtual destructor to DOMWrapperMap::Vistor
See https://android-git.corp.google.com/g/#change,21263
DOMWrapperMap::Vistor was removed and WeakReferenceMap::Visitor was added in
http://trac.webkit.org/changeset/51998
DOMWrapperMap inherits from WeakReferenceMap.
The virtual desctructor was upstreamed to webkit.org for WeakReferenceMap::Visitor in
http://trac.webkit.org/changeset/53401
Note that the message in the ChangeLog is incorrect.
Change-Id: Ia801155d0b42100e91b891b0568486fc76d037e1
|
|
|
|
| |
Change-Id: Ib24c66a3c609fd1c8ae9697f471a8abc85e5aa33
|