| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I570314b346ce101c935ed22a626b48c2af266b84
|
|
|
|
|
|
|
|
|
| |
Fixes RenderBlockLineLayout.cpp, WebViewCore.cpp and CacheBuilder.cpp
after upstream refactoring.
See http://trac.webkit.org/changeset/73618
Change-Id: I7942d6d77ce70ceb147dd711c5229c649242b10c
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
.gitignore - keep ours
Android.mk http://trac.webkit.org/changeset/74431
Parser.cpp http://trac.webkit.org/changeset/74377
ImageDecoder.cpp http://trac.webkit.org/changeset/73819
GraphicsContext.cpp http://trac.webkit.org/changeset/73729
ContextMenuItem.h http://trac.webkit.org/changeset/74028
SVGFontFaceUriElement.h http://trac.webkit.org/changeset/74493
RenderView.h http://trac.webkit.org/changeset/74524
RenderSVGResourceSolidColor.cpp http://trac.webkit.org/changeset/72926
InlineTextBox.cpp http://trac.webkit.org/changeset/73548
SliderThumbElement.cpp
RenderSlider.cpp http://trac.webkit.org/changeset/74044
StyleRareInheritedData.cpp|h
CSSStyleSelector.cpp
CSSParser.cpp http://trac.webkit.org/changeset/73219
RenderBox.h http://trac.webkit.org/changeset/73385
FrameLoader.cpp http://trac.webkit.org/changeset/73486 http://trac.webkit.org/changeset/74426
ResourceLoader.cpp http://trac.webkit.org/changeset/74453
DOMWindow.cpp|h http://trac.webkit.org/changeset/73829
HTMLLinkElement.cpp http://trac.webkit.org/changeset/74476
V8NPUtils.cpp: Do not undo http://trac.webkit.org/changeset/78994
RenderSVGResourceSolidColor.cpp http://trac.webkit.org/changeset/72926
Remove loader.cpp http://trac.webkit.org/changeset/74049
Change-Id: I8e97de5b2237d85310e1005e067f0b3a6b14432f
|
|
|
|
| |
Change-Id: I6ccd1154fa1b19c2ec2a66878eb675738735f1eb
|
|
|
|
|
|
| |
bug:4232704
Change-Id: Ia3ac8a6003c1ff7b06d2a226b3206a3be0f8c6b5
|
|
|
|
| |
Change-Id: If7093770b420b37fbb0b073c85f96e781abc55c2
|
|
|
|
|
|
|
|
|
|
|
|
| |
Force a layout of the frameview when we detect that a frames
content post flattening is wider than the original frame.
Also force a relayout of the frame as necessary to sync the
correct dimensions (i.e. when navigation occurs inside the frame)
Bug:4051085
Change-Id: Ib2543601a71b6931bb3ec4bfda75a2cac26bb2a1
|
|
|
|
|
|
|
|
|
| |
- correct support for the fullscreen button
- change the controls to be 48px high
- auto-hide the controls, touching the video makes them appear again
bug:2126902
Change-Id: Idd2b720034de3d5d432c9ea62d9045934c46f6c1
|
|
|
|
|
|
|
|
|
|
|
| |
If a layer is paginated and has a positioned grandparent,
paintPaginatedChildLayer might have an empty columnLayers vector. The logic in
updatePagination has a similar check.
Bug filed against webkit.org.
Bug: 4026385
Change-Id: I9c7de5ccab171148d26cdd187efb97d13c033ae5
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Bug:3300760
Change-Id: I44641bb4ba385ece2ace9f8dba2205b76e755289
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
revert #change,93656
Now we will use layer for fixed element in desktop site, too.
Change-Id: I0a86d46f86fa75b704286aa613e967108851b990
|
|\ |
|
| |
| |
| |
| |
| | |
bug:3466931
Change-Id: I3ce5aaef47b6135b191749b40869913f6420ce7f
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Note that we are tracking the Chromium 9.0.597 release branch,
which is WebKit r72805 + stability cherry picks.
This corresponds to r78455 on the 597 release branch.
Change-Id: I72375d9b61a767449086f0c9dc4105b2a6b62ddc
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update the layer structure during compositing sync. Make sure to turn off
scrolling if it changes.
Since I replace the content layer with a different structure, append the
children to the foreground layer so they move with the content. Remove the
clipping layer in the compositor for scrollable layers.
For children of scrollable layers, add back in the content scroll offset so that
layers are positioned relative to 0,0.
Bug: 3416512
Change-Id: I74de90aac2dcf67bd969d0b85f440343123ecab9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the previous WAR, we get the screen size from UI thread at every draw call.
That is awkward.
Now with Java side fix, we can get the screen size from setSize call now.
However, forcing a full re-layout seems like an expensive operation.
What we need to make the webkit to know the update can be done by just
updating the fixed position elements only.
So I have done these:
1. Take away the WAR by forcing the update at the convertToLayerCoord.
2. Get rid of the UI thread stuff used to tell WebViewCore the screen size.
And get rid of the redundant variables, too.
3. update the fixed element at the setSize time.
BTW, I also rename the PlatformBridge functions name.
bug: 3397602
Change-Id: I0c422ecdb570de89aecb6e568d5067acf18ecfc6
|
|
|
|
| |
This reverts commit 968791c5f1c465f0633c618fda279246ba213fdf.
|
|\
| |
| |
| |
| |
| |
| | |
pointer" into honeycomb
* commit '43f07e986c22b72e93c01c715d00755bb30f6e74':
Fix crash in RenderLayer due to null pointer
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It is possible that there is no node associated with the RenderLayer
after scroll as evidenced by the null check outside the
ANDROID_OVERFLOW_SCROLL block.
Bug: 3427863
Change-Id: Icbae7677df46eae923460d6f97a6a706f016e89d
|
| |
| |
| |
| |
| | |
bug: 3407198
Change-Id: I9902f4adf18ea181eaff284444313f47883ed7be
|
|/
|
|
|
|
|
|
| |
Bug:2754767
Enables us to remove some layering violations.
Change-Id: Iea184c7946bca9d840c708918f545a9d9b436254
|
|
|
|
|
|
| |
bug:3397602
Change-Id: I7c6c8ac8bd2c785b02cd9446730c1ca37fc71fce
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If a frame does not have a renderer, this method would attach an iframe's root
layer as the main root layer. Check for independent iframes before checking for
the renderer. Will report a bug to WebKit.org.
Bug: 3376746
Change-Id: I84bcc3e5016f6aa9d7c19a287367482df9c65c67
|
| |
| |
| |
| |
| | |
Bug:3408368
Change-Id: I21a61bd409b635e5779408f43b6265d640476c03
|
|/
|
|
|
|
|
|
|
| |
Bug:3402831
Bug:3401242
Requires a change in frameworks/base.
Change-Id: I4d7525cbf3a881fbe87f4bc624988fcb79cceab1
|
|
|
|
| |
Change-Id: I8aeef50c7b73665ec67ffeeb2194309a58de1e26
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is for fixed bottom/ right, in the zooming case.
The width and height in webkit should be calculated as the visibleRect
we use for drawing. And that is document coordinate for visible size.
Basically it is send the Rect info from webView to webViewCore.
Then at RenderBox, it will go through the PlatformBridge to pick the
info up.
Notice that the touch is not 100% working yet, the layout call in webkit
can have a early return such that fixed element layer didn't get update.
And a touch/click is not really causing the whole layout update yet.
That will be addressed in seperate change though.
bug:3404129
Change-Id: I225d41815143a05d540ed32bfc76f823603ca89c
|
|
|
|
|
|
|
|
|
| |
layers of a fixed element is actually composited...
Fixes the behaviour of the fixed toolbar on news.google.com
bug:3375416
Change-Id: I4f959ccf834dad43821f8eb6238bbd5d3b047d7f
|
|\ |
|
| |
| |
| |
| | |
Change-Id: Ia3b626a1e8608d089ad67010e3e385b428456f95
|
|\ \
| |/
|/|
| | |
honeycomb
|
| |
| |
| |
| |
| |
| |
| |
| | |
* Honeycomb-themed selection ring
* Match text selection color scheme to framework assets
Change-Id: I8a4817c7998d7009f1b00d6ad548d54545de0c78
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A new webkit merge added a couple methods to ClipRects that were not copying the
hit test rect. This make the clip rect empty during hit testing which was
clipping out all nodes in scrollable layers.
When tracking a layer, use the foreground layer if present as it will contain
the right nodes.
When looking for a scrollable layer, traverse the children in reverse drawing
order to find the top-most visible layer. This allows orkut.com to scroll.
Remove a couple of casts and headers. Use relaxAdoptionRequirement() to avoid a
RefCounted assert. Swap the texture owner hash set during deletion as release
can modify the iterator concurrently.
Update the scrollbars (even though we don't have any) when scrolling a layer to
keep the scroll position of the scrollbar in sync with the layer.
Rewrite a little bit of PluginPackageAndroid. m_module may be non-null during
load. If it is null, load the library and store it in m_module. Follow the
regular path assuming m_module is not null.
Bug: 3373179
Change-Id: If07ec9735b30c1e98e363667378a8d253a841a45
|
|
|
|
|
|
|
|
| |
Webkit is using the transformation to compute the fixed element position.
In order to simulate that, we need the Render Layer's position info.
bug:3368857
Change-Id: If15c43f76bd528b2e67ac5035c8ba4a0c803e812
|
|
|
|
|
|
|
|
| |
The scroll size will be used for layout and should respect the layer's
size change. Otherwise all the position info can be wrong.
bug:3362888
Change-Id: I553ba01ca7e5960c7ec706d56710495fc5514db1
|
|
|
|
|
|
|
|
|
|
|
|
| |
Enter compositing for iframes after all layout tasks have completed. Remember
the state of overflow scroll similar to RenderLayer so that it doesn't change
while updating the compositing state.
Return false in requiresAcceleratedCompositing if the iframe is hidden. I verified
that this fails on Safari and have submitted a bug.
Bug: 3325187
Change-Id: I20a9e1a595d14518f4c7a3e01fc1c4fa9035262c
|
|
|
|
|
|
| |
This fixes an assert and ensures that the compositor is in the correct state.
Change-Id: I7556ed998821bf2e09d89b79935e876869a584c6
|
|
|
|
|
|
| |
http://svn.webkit.org/repository/webkit/branches/chromium/597/WebCore@75681
Change-Id: Ibe552cf7af31f74b81e337eadf3d3b73a53daf60
|
|\ |
|
| |
| |
| |
| |
| | |
Bug:3085564
Change-Id: Ie570cbac6a445a337c72466598d5550c84d803ad
|
|/
|
|
|
|
|
|
|
| |
Use adoptRef when creating a new bridge item. Use
toRenderBoxModelObject instead of toRenderBox as RenderInlines have layers.
Bug: 3321493
Change-Id: I4283681eba961aedaa8d80bfdfb3d1a468aab1ac
|
|
|
|
|
| |
bug:2797422
Change-Id: Ide0867a06d61a7ee92af751ae824fe6c3b23c41f
|
|
|
|
|
|
| |
See http://trac.webkit.org/changeset/72852
Change-Id: I8ab3171330e475bec7eade78b35b11304f74579a
|
|
|
|
| |
Change-Id: I2c6f2ebc4431d15ac82b5b1a9f08159e1731bc57
|
|
|
|
|
| |
issue: 3313826
Change-Id: Ic9c87880eb6f41f72319f72123cc21cc2fe623f0
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is effectively a revert of
"Merge Webkit at r73109: render frame docWidth/docHeight method changed."
See http://trac.webkit.org/changeset/72852 and
http://trac.webkit.org/changeset/73063
Note that this is a backwards merge from Chromium release 9.0.600.0
to 9.0.597.0, to align with the Chromium 9 stable release branch.
Change-Id: I81915808439847dce87beefdd527f77962e074b5
|