| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \ \ \
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
jsc::bindings::convertValueToNPVariant fails to findroot() and passes objects as npvariant_void
* commit '686f445b3722f75d892bc87d362d148051bb433b':
Fix for bug 3324285 jsc::bindings::convertValueToNPVariant fails to findroot() and passes objects as npvariant_void
|
| |\ \ \ \
| | |/ / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
fails to findroot() and passes objects as npvariant_void
* commit 'deb796f509e2ad13b4ef4c01b1a1e707b4e762ee':
Fix for bug 3324285 jsc::bindings::convertValueToNPVariant fails to findroot() and passes objects as npvariant_void
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
findroot() and passes objects as npvariant_void
Also trying lexicalGlobalObject as root object, the comment for
lexicalGlobalObject says:
// Global object in which the currently executing code was defined.
// Differs from dynamicGlobalObject() during function calls across web browser frames.
I'm guessing that is the case here.
Webkit bug:
https://bugs.webkit.org/show_bug.cgi?id=55216
Change-Id: I61b3df93261e3688f022cde058845b1e3dfedb38
|
|\ \ \ \ \
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
fonts" into honeycomb-mr1
* commit 'abdd559eedd585db57d167929b13aa1504e22d66':
Fixed 3469204: Crash using downloaded fonts
|
| |\ \ \ \
| | |/ / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
honeycomb-mr1
* commit 'f61e9d35316897cadf1f8969a368da73f826ac02':
Fixed 3469204: Crash using downloaded fonts
|
| | |\ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This change is still pending upstream, but is being applied here now to
make it into M1 before lockdown. Track the WebKit change at:
https://bugs.webkit.org/show_bug.cgi?id=54758
When font downloading completes, CSSFontFaceSource::fontLoaded() and
CSSSegmentedFontFace::fontLoaded() called pruneTable() to reclaim
GlyphPageTreeNode memory. On Android, downloading and rendering are on
different threads and these GlyphPageTreeNodes may still be in use on
the UI thread.
This change defers freeing those GlyphPageTreeNodes until
CSSFontFaceSource and CSSSegmentedFontFace are destroyed, which occurs
on the UI thread in response to Document::scheduleForcedStyleRecalc(),
which was called by CSSFontSelector::fontLoaded().
Change-Id: Ica74e5be92c00b8c761f5d29a2310c46e62fd9eb
|
| |\ \ \ \ \
| | |/ / / /
| | | | | |
| | | | | |
| | | | | | |
* commit '9e143ba2bd15b3dd507999ba142269ab17df938a':
Do not merge.
|
| | | |/ /
| | |/| |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Remove the notion of root layers.
We were computing the root layer status incorrectly for some child layers. If an
iframe has a layer but it hasn't been attached, we might assume it is the root
layer of the tree and not produce a recording content.
Bug: 3492471
Change-Id: Ib81fb26d76742d74ebe244c34c1fab353fb9b78d
|
| |\ \ \ \
| | |/ / /
| |/| | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Part of bug:3009375
Requires a change to frameworks/base.
Change-Id: I9f5e86afff4c87e16889eadf0ad0049120885480
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We were computing the root layer status incorrectly for some child layers. If an
iframe has a layer but it hasn't been attached, we might assume it is the root
layer of the tree and not produce a recording content.
Bug: 3492471
Change-Id: I83d33d991d53108110f99fc2d33d58713b50a695
|
|\ \ \ \ \
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
given focus." into honeycomb-mr1
* commit '1bf24f66d840a3fb19c34fd445d6bc5d9b352755':
ensure plugins draw correctly even when they have been given focus.
|
| |\ \ \ \
| | |_|/ /
| |/| | |
| | | | | |
into honeycomb-mr1
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The initial attempt at fixing this bug was to modify the clip, but
this was not correct and only fixed cases where the plugin was on
the left edge of the screen. This CL properly adjusts the plugin's
boundaries to make sure the content is drawn in the appropriate
position.
bug: 3477581
Change-Id: I5958228a93fa5600cd7e24ed9e7e1e26f6b241bc
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Wait the remaining of the 60FPS cap delay rather than not paint.
Returning true if called faster than 60FPS means
we are not drawing and ask for the framework to call
us again; this works in general because the framework recopy
the previous framebuffer. But in some cases, it didn't, causing
the webview to flicker. A correct fix would be to introduce
the capping in framework rather than try to doing it in the
webview; in the meantime we will sleep the remaining of the delay
as a workaround, so that we still provide the GPU
benefits we wanted (at >60FPS the GPU was being saturated in
some cases).
bug:3500655
Change-Id: Ibaa1d93e0a13433a2c842b19b58538894fdaa7e4
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug:3009375
Update the button assets for WebView, and use the nine patch
data stored in the bitmap to draw them.
Requires a change to frameworks/base.
Change-Id: Ibe61dc9c06c49b2a69a74152d2a89fb1731ad017
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Returning true if called faster than 60FPS means
we are not drawing and ask for the framework to call
us again; this works in general because the framework recopy
the previous framebuffer. But in some cases, it didn't, causing
the webview to flicker. A correct fix would be to introduce
the capping in framework rather than try to doing it in the
webview; in the meantime we will sleep the remaining of the delay
as a workaround, so that we still provide the GPU
benefits we wanted (at >60FPS the GPU was being saturated in
some cases).
bug:3500655
Change-Id: I9942e8e47f82a7485cc1ec4ba4db81c5ad45d4cd
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
https://android-git.corp.google.com/g/40387 fixed a long-standing bug to
avoid leaking references to injected Java objects. However, it did so by
making changes to JavaNPObjectV8.cpp/h which were never upstreamed. This
change avoids the need for these changes.
This change also avoids the use of a local PassRefPtr, which was
incorrectly introduced in https://android-git.corp.google.com/g/36204.
Change-Id: I6b17e85f7991e5226e00e7b041c38e2ca3d0cf57
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: I21555e923ba6ac6c2bcd291ffa73a1aa087bdb3b
|
|\ \ \ \
| |/ / / |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
bug: 3477581
Change-Id: Ia7bbaaca405db33dbefaa8f6f00e9250580e5f7b
|
|\ \ \ \
| |/ / /
|/| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The dtor of GLWebViewState is calling the dtor of its TiledPage
variables; the dtor of TiledPage wait until any pending painting
operations running in the TextureGenerator thread are done. The painting
operations ultimately paint using the current GLWebViewState's base
layer. We were doing unref() on the baselayer before destroying the
TiledPage...
bug:3429924
Change-Id: I685e7fca5e5bae796f808debbf7e4ce668b83e6b
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If we detect an OOM from GL, crash the process to stop the
framework falling back to software rendering. The framework will
not enable HW rendering again until the process is killed and
Flash does not work with software rendering.
Bug: 3477085
Change-Id: I8defebbe3ea281c342fc99ace8638c347a3eb246
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This reverts commit 2879037f2d6c595b8c16e992462ce5ca60d8fdba.
Revert the original work around as the underlying problem is fixed
with I2747dd4630a2a7dc18eae4c5fde36fd14c461747
Change-Id: Ibc1e997bca2aadc27527b6980de38603e6971770
|
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: Id6e0b8199f82c44de0e7b1b7e7eb42bdb96bf908
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Each view will now be capped at 60fps. The previous code would
either starve the drawing of additional webviews or would draw
them at a rate of 60fps/N where N is the number of webviews.
Change-Id: I5698d610b17d4c8cfe137c51c2b978dae04ae1cf
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Change-Id: Ifb290ab8e027b1828c1c10ca3ee70eadedf23f66
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
bug: 2968415
Change-Id: Ie67c9f6b28a81d4a65f39bde2896078d7b49b8ee
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
* changes:
Merge WebKit at Chromium 9.0.597.107: Update WebKit merge revision
Merge WebKit at Chromium 9.0.597.107: Initial merge by git.
|
| | |_|/ / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Note that we are tracking the Chromium 9.0.597 release branch,
which is WebKit r72805 + stability cherry picks.
This corresponds to r78920 on the 597 release branch.
Change-Id: I610ebdbcba92cfa788b229ee207a405789d45e67
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
Change-Id: I1b6be15a38d2afc55659872b82e13ebcd8fd2ada
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Bug:3300760
Change-Id: I44641bb4ba385ece2ace9f8dba2205b76e755289
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Ensure that we wait in a while loop checking the condition when
we call wait, and only signal after unlocking the Mutex.
Also removes mNewRequest lock and condition in the TexturesGenerator
as it doesn't seem to be needed.
Hopefully this will clear up some ANRs.
Change-Id: I1b8b103a6effd2aa678a304e2519a6f6c484aaad
|
|\ \ \ \ \ |
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Do not expand frames that cannot scroll. Use contentsWidth and contentsHeight
instead of exposing docWidth. Trigger a layout of the parent if the FrameView's
layout reveals a larger content dimension. Remove iframe flattening code.
Bug: 3370518
Bug: 3323913
Change-Id: I60e89caf335bfaf271f90ffd538c65f3735572da
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Uses new skia api to identify fixed width fonts. Without this fix, all
Android fonts were reported as variable width, causing layout
adjustment of whitespace. Now that fixed width fonts are properly
reported, space characters preserve the same width as non-space chars.
Change-Id: I7d83481f44e6c34fd8ae5c6638b1625d3a83a637
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
flash plugin..."
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
the GPU and the flash plugin...
bug:3471680
Change-Id: I436de6caea4dd5b1171f260d328dfe8170463832
|