summaryrefslogtreecommitdiffstats
path: root/Source/WebCore/rendering
Commit message (Collapse)AuthorAgeFilesLines
* am f912aaa3: am 599c05f3: Merge "Revert "Put canvas on a layer"" into ics-mr1John Reck2011-12-132-7/+1
|\ | | | | | | | | * commit 'f912aaa3c8084eccb0f5fcb74606063d9ce5c74b': Revert "Put canvas on a layer"
| * Merge "Revert "Put canvas on a layer"" into ics-mr1John Reck2011-12-132-7/+1
| |\
| | * Revert "Put canvas on a layer"John Reck2011-12-132-7/+1
| | | | | | | | | | | | Bug: 5712065 This reverts commit 35e0b8dd7902e92f50ede4df2e4bad4ed581b770
* | | Fix the repaint inval mechanism for layers - cherry-pick from MR1Nicolas Roard2011-12-091-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We only keep the scrollable layers invalidating their entire area instead of incurring this penalty for *all* layers. Also remove unnecessary repaint when scrolling (we have the entire content on the UI side already). While the entire scrollable area will be invalidated and marked as dirty, the existing code in PaintedSurface already only look at the visible tiles of scrollable layers to consider the layer's content as being ready to display, so the real world penalty (while far from optimal) is limited. Implementing the correct approach (only invalidating what really changed on scrollable layers) would sadly be a lot more complex, as currently webkit will *not* send us the repaint invals if they are on a currently clipped area, as webkit's default behaviour to implement scrolling of such element is to repaint them anyway... bug:5721618 Change-Id: I9af240d5f42f00f9ab07710e43ef8d72dfaf8155
* | | am e50c6da1: Merge "Revert change that caused text in floating divs to not ↵Mangesh Ghiware2011-12-071-1/+1
|\ \ \ | |/ / | | | | | | | | | | | | | | | reflow." into ics-mr1 * commit 'e50c6da15806ff91b5e9298cb303f2b8f9ae6b35': Revert change that caused text in floating divs to not reflow.
| * | Merge "Revert change that caused text in floating divs to not reflow." into ↵Mangesh Ghiware2011-12-071-1/+1
| |\ \ | | | | | | | | | | | | ics-mr1
| | * | Revert change that caused text in floating divs to not reflow.Mangesh Ghiware2011-12-071-1/+1
| | | | | | | | | | | | | | | | | | | | Bug: 5455817 (Text reflow not working in browser) Change-Id: I2a62a7fb4c7acde640cd87b8d0f03200b8f7fc2f
| * | | Fix the repaint inval mechanism for layers - DO NOT MERGENicolas Roard2011-12-071-0/+7
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We only keep the scrollable layers invalidating their entire area instead of incurring this penalty for *all* layers. Also remove unnecessary repaint when scrolling (we have the entire content on the UI side already). While the entire scrollable area will be invalidated and marked as dirty, the existing code in PaintedSurface already only look at the visible tiles of scrollable layers to consider the layer's content as being ready to display, so the real world penalty (while far from optimal) is limited. Implementing the correct approach (only invalidating what really changed on scrollable layers) would sadly be a lot more complex, as currently webkit will *not* send us the repaint invals if they are on a currently clipped area, as webkit's default behaviour to implement scrolling of such element is to repaint them anyway... bug:5721618 Change-Id: Ia470157c716fa1c557e4a196ba014296ad9e627a
* | | am 42e97318: Merge "A WAR to enable the slider touch event on youtube.com" ↵Bart Sears2011-11-301-0/+7
|\ \ \ | |/ / | | | | | | | | | | | | | | | into ics-mr1 * commit '42e973186ecf6f1a040f14b7169bb99e0f100563': A WAR to enable the slider touch event on youtube.com
| * | Merge "A WAR to enable the slider touch event on youtube.com" into ics-mr1Bart Sears2011-11-301-0/+7
| |\ \
| | * | A WAR to enable the slider touch event on youtube.comTeng-Hui Zhu2011-11-221-0/+7
| | | | | | | | | | | | | | | | | | | | bug:5520141 Change-Id: Ib346c42037f68b5e8303f0c61196fb28e698f7c9
* | | | am 807ee5ec: Merge "synchronize animation starts with webkit" into ics-mr1Chris Craik2011-11-301-0/+5
|\ \ \ \ | |/ / / | | | | | | | | | | | | * commit '807ee5ec662a7864dee505040ade9a9b3eab143c': synchronize animation starts with webkit
| * | | synchronize animation starts with webkitChris Craik2011-11-291-0/+5
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | bug:5239801 this better supports animations not synchronous with webkit Relies on the frameworks/base CL: https://android-git.corp.google.com/g/#/c/152533/ Change-Id: Ia79a475065b3891db8fc4014559062ab1ac95ebe
* | | am 64797036: Merge "Put canvas on a layer" into ics-mr1John Reck2011-11-282-1/+7
|\ \ \ | |/ / | | | | | | | | | * commit '647970367ac56d95e84fbfca92d8b7390d5d2fed': Put canvas on a layer
| * | Put canvas on a layerJohn Reck2011-11-282-1/+7
| | | | | | | | | | | | | | | | | | Bug: 5666191 Change-Id: I30708d508b7e05e8bcbc6c22413134ca378f6d2c
* | | am 7839f0a8: Fix SVG text renderingSteve Block2011-11-241-0/+20
|\ \ \ | |/ / | | | | | | | | | * commit '7839f0a8c60340239148921eb35c3e2afc750701': Fix SVG text rendering
| * | Fix SVG text renderingSteve Block2011-11-241-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Android's implementation of GraphicsContext::setCTM() is broken, because Skia's Picture mode does not support setMatrix(). This broken code was added in https://android-git.corp.google.com/g/#/c/112636 as part of the merge to WebKit r80534. This change modifies SVGInlineTextBox to avoid calling GraphicsContext::setCTM() and makes clear that the method should not be used. Bug: 5590123 Change-Id: I45a3c8c356b7f068bb943a45b9f10cbc041331e2
* | | am 3eaf0f8c: Force layers above overscroll/fixed elements to compositeChris Craik2011-11-231-8/+0
|\ \ \ | |/ / | | | | | | | | | * commit '3eaf0f8cdb150a43732c8391a73046811b3c378d': Force layers above overscroll/fixed elements to composite
| * | Force layers above overscroll/fixed elements to compositeChris Craik2011-11-221-8/+0
| |/ | | | | | | | | | | | | | | | | bug:5480098 This fixes the case where they were drawn on the base layer, beneath overscroll elements. Change-Id: If9dda8c3a25cf38e777847b834ae02ec530a8000
* | am e2e7333b: Merge "Only allow stacking contexts to skip compositing" into ↵Bart Sears2011-11-181-1/+1
|\ \ | |/ | | | | | | | | | | ics-mr1 * commit 'e2e7333b68070e867d6d96f46bedd49eb85199a0': Only allow stacking contexts to skip compositing
| * Only allow stacking contexts to skip compositingChris Craik2011-11-171-1/+1
| | | | | | | | | | bug:5635942 Change-Id: Ibda67bb638d9fca5f32c85ee39c1ae1429986eda
* | Merge "Removing ANDROID_INSTRUMENTATION code"Kristian Monsen2011-11-172-11/+0
|\ \
| * | Removing ANDROID_INSTRUMENTATION codeKristian Monsen2011-11-172-11/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This has not been used for years, and due to WebKit merges the results are not accurate anymore. The resulting code is cleaner, less likely to create merge conflicts, and does not give the impression that this can be turned on and it will still work. Needs CL: https://android-git.corp.google.com/g/#/c/148912/ Change-Id: I617ad00c103ab72038371a3203452d2ccec0e50c
* | | am d34224ca: Merge "Promote -ve z-index fixed/scrollable elements to layers" ↵Ben Murdoch2011-11-171-0/+11
|\ \ \ | |/ / |/| / | |/ | | | | | | into ics-mr1 * commit 'd34224ca67791aa7215160c7be4900f965f79eea': Promote -ve z-index fixed/scrollable elements to layers
| * Promote -ve z-index fixed/scrollable elements to layersBen Murdoch2011-11-161-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We normally do not necessarily promote fixed or scrollable elements to compositing layers to try and reduce the number of layers that get created. However in the case that such an element appears in the negative z-order, we must do the promotion to ensure that the layer is painted at the correct z-index in the hierarchy (i.e not too high - sites like to use a fixed image with z-index:-1 to implement a fixed background -- without this patch we end up painting the background over the main page content). Bug: 5152567 Change-Id: I36bfe14660a33d45ad54552ae41b9d7157f8dabf
| * Don't force composited layers to be stacking contexts - DO NOT MERGEChris Craik2011-10-251-1/+1
| | | | | | | | | | | | | | | | | | | | bug:5264240 Was causing crashes, and layer ordering problems. Cherry-pick of b8c237486bcf299d8a04bdae8d8e35fd37866172 Change-Id: I1f76516d4e313101ea9c90759ee63d4cef2d6ced
* | Cherry-pick WebKit change 87687 to fix debug buildSteve Block2011-10-281-0/+1
| | | | | | | | | | | | | | See http://trac.webkit.org/changeset/87687 Bug: 5448972 Change-Id: I1f2da8f5a2264ce6627dc99ebe1b235ae34f7c62
* | Merge "Don't force composited layers to be stacking contexts"Chris Craik2011-10-241-1/+1
|\ \ | |/ |/|
| * Don't force composited layers to be stacking contextsChris Craik2011-10-211-1/+1
| | | | | | | | | | | | | | | | bug:5264240 Was causing crashes, and layer ordering problems. Change-Id: I1f76516d4e313101ea9c90759ee63d4cef2d6ced
* | Cherry pick 97075John Reck2011-10-204-27/+15
| | | | | | | | | | | | Bug: 5491444 Change-Id: If97d58a3d590e8e972bceec61e3ae16860a30088
* | Cherry pick 94857John Reck2011-10-201-2/+7
|/ | | | | | Bug: 5491573 Change-Id: I32666ca6abdc2e224e6b9727f65e62fd3bd10859
* Cherry-pick WebKit change 89836 to fix a crash due to floats not being removedSteve Block2011-10-141-0/+3
| | | | | | | | | This is part 2 of 2 of the fix. See http://trac.webkit.org/changeset/89836 Bug: 5249309 Change-Id: If23a41a8e75e5fb6ba9e84e481ca44a319f678ef
* Cherry-pick WebKit change 89165 to fix a crash due to floats not being removedSteve Block2011-10-142-4/+39
| | | | | | | | | This is part 1 of 2 of the fix. See http://trac.webkit.org/changeset/89165 Bug: 5249309 Change-Id: I1159aab70e1fa6d3025761423c4164682dc97b64
* allow for compositing of 1x1 pluginsChris Craik2011-10-031-0/+6
| | | | | | bug:5382635 Change-Id: I0da21245ec7808da452941a45ae5008e278f3007
* Roll back fix for http://b/issue?id=4203823Ben Murdoch2011-09-081-4/+1
| | | | | | | | | | Allow positioned divs with overflow to scroll. Keeps tidying up that fix for http://b/issue?id=4203823 did and rolls back the functional change. Bug: 5216561§ Change-Id: I6268bbe880c432c87ca04e68697f66b32b7032d0
* Cherry-pick WebKit change 92744 to fix RenderObjectChildListSteve Block2011-09-071-1/+1
| | | | | | | See http://trac.webkit.org/changeset/92744 Bug: 5263877 Change-Id: I672c48d3fb6dc90d0721b6c5638070eb944596f4
* Cherry-pick WebKit change 85623 to fix RenderInline::culledInlineAbsoluteQuads()Steve Block2011-09-061-0/+5
| | | | | | | See http://trac.webkit.org/changeset/85623 Bug: 4986300 Change-Id: If557cbd8c6914dc6875b87cfe04591f9bfa42047
* Incorrect handling of 'display:' property within nested <ruby> tagsSteve Block2011-09-021-14/+34
| | | | | | | | This is a cherry-pick of http://trac.webkit.org/changeset/89987 Bug: 5244760 Change-Id: Iebbac8a93d6aabd0f8d568c9b1ace6f9316a6b6c
* Remove some unsafe static_cast in rendering/Steve Block2011-09-021-4/+4
| | | | | | | | | | | This is a partial cherry-pick of http://trac.webkit.org/changeset/89304 It is required to allow us to cherry-pick http://trac.webkit.org/changeset/89987 Bug: 5244760 Change-Id: I854067cbc297e667ec432f947a268eef5c4dfa0f
* Part of fix for bug 5152544 Reduce the number of warning, int and size_tKristian Monsen2011-08-111-3/+3
| | | | | | Don't compare and use size_t with int Change-Id: I08b329cdb192fa031acae5a90cd6ad6d8ec39aea
* Previous commit was missing a chunk of code...Nicolas Roard2011-08-081-0/+3
| | | | | bug:5121768 Change-Id: Ie0065bca023b9a8470970ba15f5837f600fe4afb
* Fix crashes on plus.google.com and reduce the number of necessary layersNicolas Roard2011-08-051-4/+20
| | | | | bug:5121768 Change-Id: I616af5cdc3f8b0a790fd50434c919b2c95b0e486
* Reduce the number of layersNicolas Roard2011-07-294-39/+112
| | | | | | | | | | | | - overflow elements triggered all layers before them to be composited; this is not needed at all... - fixed elements will trigger layers after them to be composited, but we don't need to composite all of them -- the one fully contained into previous composited layers don't need to... bug:5069090 Change-Id: I65f789f490b837a16096b4cb186c45ade1605b41
* Refactor the overflow scroll fix.Shimeng (Simon) Wang2011-07-251-7/+10
| | | | | | | Hope this is more understandable. issue: 4203823 Change-Id: Ib1d95f6b250baf4b94f706e090a9f087aa9b7ed8
* Disable customized overflow scroll for positioned renderblock.Shimeng (Simon) Wang2011-07-251-4/+7
| | | | | | | | | | This fixes maps.google.com dropdown list scrolling issue. Tested on developer.android.com, slate.com, lemonde.fr; the existing overflow scrolling are working as before this change. issue: 4203823 Change-Id: I11cebbfd8bb3dd060bbee1b29ec96627fcbf1a72
* Limit RTL text wrapping when having floating element.Shimeng (Simon) Wang2011-07-211-1/+1
| | | | | issue: 5047703 Change-Id: Ie7d9bb54649afb4d025d4ec02bcc42b52b4049d1
* Add android specific virtual function to GraphicsLayerClient.Shimeng (Simon) Wang2011-07-142-9/+3
| | | | | | | | | | | | | | | This lets the GraphicsLayerClient instance decides whether it has owning RenderLayer, instead of using static_cast. This makes overflow'ed iframe scrollable again. This change also reverts Tenghui's CL: https://android-git.corp.google.com/g/#change,115508 Tested on scrollable iframe and inline video. issue: 4902019 Change-Id: I252f5432b0750c5cac0a4404663e1730ef006cfc
* Merge WebKit at branches/chromium/742 r89068: Initial merge by Git.Ben Murdoch2011-07-132-13/+23
| | | | | | Take us to top of Chrome 12 release branch (12.0.742.130) Change-Id: I4408a97e343a118cf4a1bb9d71367bcc2c16ae48
* Better way to determine not to reflow.Shimeng (Simon) Wang2011-06-231-2/+2
| | | | | | | | | 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
* Do not reflow text if a div has border.Shimeng (Simon) Wang2011-06-231-1/+1
| | | | | | | | 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
generated by cgit v1.1 at 2024-09-14 10:25:55 +0000