summaryrefslogtreecommitdiffstats
path: root/cc
Commit message (Collapse)AuthorAgeFilesLines
...
* ui: Remove gfx::Size::ClampToNonNegative, prevent negative sizes always.danakj@chromium.org2012-11-121-1/+1
| | | | | | | | | | | | | | | | This was added with the intention of using Size as a vector, replacing use of IntSize. Since we have Vector2d now, negative sizes should not exist, so clamp them in set_width/set_height and the constructor. Not covered by tests, as we can't test DCHECKs. TBR=sky BUG=160158 Relanding: https://codereview.chromium.org/11365160/ Review URL: https://codereview.chromium.org/11410024 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167255 0039d316-1c4b-4281-b951-d872f2087c98
* ui: Add SkIRectToRect() function to convert from SkIRect type to gfx::Rect.tfarina@chromium.org2012-11-122-20/+14
| | | | | | | | | | | This fixes the 3 TODOs for Dana from region.* TEST=cc_unittests,ui_unittests R=danakj@chromium.org Review URL: https://codereview.chromium.org/11410025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167244 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Guard overdraw metrics behind the --trace-overdraw command-line flag.danakj@chromium.org2012-11-128-17/+54
| | | | | | | | | | | | | | | | | Because these metrics are slow, they change the characteristics of traces. When we want to look at performance, then these become misleading. So, enable them only when desired, when someone wants tracing information about overdraw. Also reverting changes made to make the overdraw metrics faster and less precise. Since they are optional, we should get the most accurate data out of them when they are turned on. BUG=159718 R=enne,jamesr Review URL: https://codereview.chromium.org/11369188 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167228 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Fix header include guards.tfarina@chromium.org2012-11-119-29/+35
| | | | | | | | | | | | | | | Fixed the files found by the following command lines: $ cpplint.py cc/* 2>&1 | grep header_guard $ cpplint.py cc/test/* 2>&1 | grep header_guard BUG=144576,144577 TEST=cc_unittests TBR=enne@chromium.org,jamesr@chromium.org Review URL: https://chromiumcodereview.appspot.com/11365188 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167123 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Remove the remaining using-directives of namespace cc.tfarina@chromium.org2012-11-103-3/+24
| | | | | | | | | | | | | | | Fixed the entries found by the following command lines: $ git grep -n "using namespace cc" cc/ $ cpplint.py cc/test/* 2>&1 | grep using BUG=144576,144577 TEST=cc_unittests TBR=enne@chromium.org,jamesr@chromium.org Review URL: https://chromiumcodereview.appspot.com/11312181 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167110 0039d316-1c4b-4281-b951-d872f2087c98
* Introduce Tile Versionsnduca@chromium.org2012-11-105-28/+197
| | | | | | | | | BUG=155209 Review URL: https://chromiumcodereview.appspot.com/11364194 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167079 0039d316-1c4b-4281-b951-d872f2087c98
* ui: Make gfx::Size::Scale() mutate the class. Add gfx::ScaleSize() similar ↵danakj@chromium.org2012-11-105-16/+12
| | | | | | | | | | | | | | to Rect/Point. Covered by existing unit tests. R=sky BUG=160158 Review URL: https://chromiumcodereview.appspot.com/11377068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167077 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Remove forbidden using namespace directives.tfarina@chromium.org2012-11-1047-109/+139
| | | | | | | | | | | BUG=144576,144577 TEST=cc_unittests R=enne@chromium.org,jamesr@chromium.org,danakj@chromium.org Review URL: https://chromiumcodereview.appspot.com/11410022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167073 0039d316-1c4b-4281-b951-d872f2087c98
* Remove WTF and WebCore from cc/ and webkit/compositor_bindings/piman@chromium.org2012-11-10172-392/+25
| | | | | | | | | | | Ding, dong... BUG=154451 Review URL: https://chromiumcodereview.appspot.com/11410021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167071 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 167062 - ui: Remove gfx::Size::ClampToNonNegative, prevent negative ↵danakj@chromium.org2012-11-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | sizes always. This was added with the intention of using Size as a vector, replacing use of IntSize. Since we have Vector2d now, negative sizes should not exist, so clamp them in set_width/set_height and the constructor. R=sky BUG=160158 Review URL: https://codereview.chromium.org/11365160 TBR=danakj@chromium.org Apparently there are now Aura unit tests that rely on negative sizes: http://build.chromium.org/p/chromium.win/buildstatus?builder=Win%20Aura&number=24205 Review URL: https://codereview.chromium.org/11275243 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167066 0039d316-1c4b-4281-b951-d872f2087c98
* ui: Remove gfx::Size::ClampToNonNegative, prevent negative sizes always.danakj@chromium.org2012-11-101-1/+1
| | | | | | | | | | | | | This was added with the intention of using Size as a vector, replacing use of IntSize. Since we have Vector2d now, negative sizes should not exist, so clamp them in set_width/set_height and the constructor. R=sky BUG=160158 Review URL: https://codereview.chromium.org/11365160 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167062 0039d316-1c4b-4281-b951-d872f2087c98
* Delete ThreadChecker from FontAtlas.aelias@chromium.org2012-11-102-10/+0
| | | | | | | | | | | This object is created on the main thread and used on the impl thread. BUG=160312 Review URL: https://chromiumcodereview.appspot.com/11360178 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167057 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Prevent small scale factors (below 1) from being used or saved as the ↵danakj@chromium.org2012-11-102-1/+60
| | | | | | | | | | | | | | | | | layer's rasterScale. When the scale is < 1, then we don't save anything. The first time we see a scale >= 1, we will save it. Tests: cc_unittests:LayerTreeHostCommonTest.verifySmallContentsScale BUG=159655 R=enne,jamesr Review URL: https://chromiumcodereview.appspot.com/11377088 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167040 0039d316-1c4b-4281-b951-d872f2087c98
* Avoid setting activeTexture redundantlyjamesr@chromium.org2012-11-106-10/+121
| | | | | | | | | | | | We use GL_TEXTURE0 for nearly all operations, so it's cheaper to leave this as the default for all draws and have quads that use other texture units reset to 0. BUG= Review URL: https://chromiumcodereview.appspot.com/11275222 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167030 0039d316-1c4b-4281-b951-d872f2087c98
* ui: Add methods to clamp Sizes, Points, and Vectors from above or below.danakj@chromium.org2012-11-105-60/+12
| | | | | | | | | | | | | | | | | | Tests: PointTest.Clamp PointTest.ClampF SizeTest.Clamp SizeTest.ClampF Vector2dTest.Clamp Vector2dTest.ClampF Vector3dTest.ClampF R=sky,enne BUG=147395 Review URL: https://codereview.chromium.org/11361186 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167014 0039d316-1c4b-4281-b951-d872f2087c98
* ui: Prefer +/- operators to apply offsets.danakj@chromium.org2012-11-104-30/+19
| | | | | | | | | | | | | | | | | Adds +/- operators to gfx::Rect that are applied to its origin Point. Removes gfx::Point method a.OffsetFrom(b) in favor of (b - a). Begin use +/- instead of Offset() in ui/gfx/ and cc/ New tests: ui_unittests:RectTest.Offset R=pkasting,enne BUG=158416 Review URL: https://codereview.chromium.org/11293194 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167012 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Make Picture/PicturePile handle recording/rasterenne@chromium.org2012-11-098-28/+230
| | | | | | | | | | | | | | | It's not efficient (or tested), but this should be enough to start being useful once we add the raster/upload/appendQuads path. Next steps are probably to add tilings to the PictureLayerImpl. R=nduca@chromium.org BUG=155209 Review URL: https://chromiumcodereview.appspot.com/11293188 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166999 0039d316-1c4b-4281-b951-d872f2087c98
* Uber Comp: never change mailbox name associated with a texture object.apatrick@chromium.org2012-11-095-46/+35
| | | | | | Review URL: https://codereview.chromium.org/11366123 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166995 0039d316-1c4b-4281-b951-d872f2087c98
* ui: Add non-member Vector2dScale() and Vector3dScale() methods to create ↵danakj@chromium.org2012-11-093-23/+5
| | | | | | | | | | | | | | | | | scaled vectors These behave like similar methods for Rect/Point/Size. Tests: ui_unittests:Vector2dTest.Scale ui_unittests:Vector3dTest.Scale R=sky BUG=160158 Review URL: https://codereview.chromium.org/11293193 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166993 0039d316-1c4b-4281-b951-d872f2087c98
* Plumb through cropped output size for VideoFramesheu@chromium.org2012-11-0910-97/+143
| | | | | | | | | | | | | | | | | | | | | | | | The video playback path needs to be able to handle cropped video frames, e.g. for HW decoders that output to macroblock-rounded buffer sizes. * Composite only the visible subrect from WebVideoFrame in cc::VideoLayerImpl * Remove some extraneous cropping logic from cc::VideoLayerImpl now that we have exact cropping info. * media::VideoFrame replaces "data_size_" member with "coded_size_", and adds a "visible_rect_" gfx::Rect to indicate the sub-rect of the entire frame that should be visible (after cropping) * Associated changes to various decoder/capture pipelines to plumb this through. TEST=build, run on x86, ARM BUG=155416,140509,chrome-os-partner:15230 Change-Id: I284bc893959db427bc9ae677aed8b07292d228ae Review URL: https://chromiumcodereview.appspot.com/11269017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166988 0039d316-1c4b-4281-b951-d872f2087c98
* ui: Make gfx::Point::Scale() mutate the class, similar to gfx::Rect.danakj@chromium.org2012-11-092-9/+9
| | | | | | | | | | | | | | We add gfx::ScalePoint() as a non-mutating version of the Scale method. Tests: ui_unittests:PointTest.Scale R=sky BUG=160158 Review URL: https://codereview.chromium.org/11369144 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166979 0039d316-1c4b-4281-b951-d872f2087c98
* Extra logging for NinePatch layers in layerTreeAsText()jamesr@chromium.org2012-11-094-15/+14
| | | | | | | | | BUG= Review URL: https://chromiumcodereview.appspot.com/11366135 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166974 0039d316-1c4b-4281-b951-d872f2087c98
* If a layer contains a filter, flush the compositor context before the filtersenorblanco@chromium.org2012-11-091-0/+5
| | | | | | | | | | | bitmap goes out of scope. BUG=159874 Review URL: https://chromiumcodereview.appspot.com/11365172 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166963 0039d316-1c4b-4281-b951-d872f2087c98
* Adding hooks for gathering total pixels painted and rasterized stats.hartmanng@chromium.org2012-11-096-19/+43
| | | | | | | | | | Blocked on: https://bugs.webkit.org/show_bug.cgi?id=98269 BUG=156087 Review URL: https://chromiumcodereview.appspot.com/10982078 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166911 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Expose clear and swap on Regionenne@chromium.org2012-11-095-16/+59
| | | | | | | | | | R=danakj@chromium.org BUG=none Review URL: https://chromiumcodereview.appspot.com/11368156 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166866 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Rewrite PageScaleAnimation for new coordinate system.aelias@chromium.org2012-11-095-171/+245
| | | | | | | | | | | | | | | | | | | | | - I moved PageScaleAnimation to work entirely at root content layer scale, to be consistent with the new pinch zoom code. This avoids the need for any scaling of scroll offsets. However, everything must now be in floating point, and the complexity is moved into viewport size calculation instead. - I also took the opportunity to add support for two anchors instead of just one, introducing an additional level of interpolation. This makes the animation appear less jarring when we clamp it to document edge, and it also removes the need for special-casing translation-only animations. BUG=152505 Review URL: https://chromiumcodereview.appspot.com/11090062 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166855 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Rename MockContentLayerClient to FakeContentLayerClient and move to cc/test/danakj@chromium.org2012-11-094-28/+68
| | | | | | | | | | | | | | This class is used as a fake, not a Mock. Move it out so it possible to use this outside of layer_tree_host_unittest. Covered by existing tests. R=enne TEST=cc_unittests Review URL: https://chromiumcodereview.appspot.com/11312155 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166842 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Add some early outs to avoid expensive operationsdanakj@chromium.org2012-11-092-2/+11
| | | | | | | | | | | | | | | | | | | | | | | | mapHomgenousPoint is not cheap. We can do faster in projectClippedRect similar to mapClippedRect. rectSubtractRegion constructs a Region to do subtraction from. If the subtraction's rvalue is empty, then there is nothing to do and we can avoid creating a Region structure at all. I measured time spent in calculateRenderPasses with a draw-heavy unit test. Baseline: 0.001148 seconds With these changes: 0.001116 seconds So, about 3% reduction in time spent in calculateRenderPasses. R=enne BUG=159718 Review URL: https://chromiumcodereview.appspot.com/11312154 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166841 0039d316-1c4b-4281-b951-d872f2087c98
* Disable scissor test during texture copiesjamesr@chromium.org2012-11-092-3/+12
| | | | | | | | | BUG=160075 Review URL: https://chromiumcodereview.appspot.com/11368152 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166835 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Define Region::Contains() to be A contains B if all points in B are also ↵danakj@chromium.org2012-11-093-2/+9
| | | | | | | | | | | | | | | | in A. This means that Contains(empty) is always true. Tests: RegionTest.Contains R=enne Review URL: https://chromiumcodereview.appspot.com/11368149 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166812 0039d316-1c4b-4281-b951-d872f2087c98
* [cc] Tiles and tile manager for impl side paintingnduca@chromium.org2012-11-086-0/+208
| | | | | | | | | | BUG=155209 R=enne@chromium.org Review URL: https://chromiumcodereview.appspot.com/11369130 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166787 0039d316-1c4b-4281-b951-d872f2087c98
* cc: The SolidColorLayer should report contentsOpaque() true when its color ↵danakj@chromium.org2012-11-084-1/+66
| | | | | | | | | | | | | | | | | is opaque This is required for the layer to occlude other things. Currently the layer never occludes anything. Tests: cc_unittests:SolidColorLayerImplTest.verifyOpaqueRect BUG=159745 R=jamesr Review URL: https://codereview.chromium.org/11360145 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166690 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Rename Texture class to Resource.reveman@google.com2012-11-0822-105/+105
| | | | | | | | | | | Renames Texture to Resource and ScopedTexture to ScopedResource. BUG= TEST=cc_unittests Review URL: https://codereview.chromium.org/11377055 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166689 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Do not save the rasterScale for layers until they are finished animating ↵danakj@chromium.org2012-11-085-38/+89
| | | | | | | | | | | | | | | | | | | transforms. Currently we save the rasterScale for a layer the first time we see it. However, if the layer is animating, the value we save isn't very accurate. Instead, avoid saving the value until the animation is complete. Tests: cc_unittests:LayerTreeHostCommonTest.verifyContentsScaleForAnimatingLayer R=enne BUG=159937 Review URL: https://chromiumcodereview.appspot.com/11362151 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166660 0039d316-1c4b-4281-b951-d872f2087c98
* Remove DirectRenderer::disableScissorTest, always leave GL_SCISSOR_TEST ↵jamesr@chromium.org2012-11-086-23/+8
| | | | | | | | | | | | | | | enabled in GlRenderer Constantly calling glEnable(GL_SCISSOR_TEST) costs us a few ms/frame on some hardware. As it turns out, we never disable the scissor test so we can just leave it on all the time. BUG= Review URL: https://chromiumcodereview.appspot.com/11378004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166632 0039d316-1c4b-4281-b951-d872f2087c98
* Remove static thread pointers from CC, attempt 3aelias@chromium.org2012-11-0862-616/+666
| | | | | | | | BUG=152904 Review URL: https://chromiumcodereview.appspot.com/11232051 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166627 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Create a Region class that wraps SkRegion, to replace use of ↵danakj@chromium.org2012-11-0828-501/+928
| | | | | | | | | | | | | | | | | | | | | | | | | | | WebCore::Region. We create a class in cc/ called Region which provides a gfx:: type-friendly API to SkRegion, and allows for easily swapping out region implementations in the future if required. During the process, I removed tests dependency on a "size()" method on Region, that used to give the number of rects in the Region's internal representation. Instead, we always create a Region in the tests from our expected rects, and compare the Regions directly. We use ToString() comparisons to get useful failure outputs, similar to the unit tests of other geometry types in ui/gfx. This uncovered a WTF::Vector holdout in the OcclusionTracker class, which is converted to a std::vector. Covered by existing tests; no change in behaviour. R=enne BUG=147395 Review URL: https://chromiumcodereview.appspot.com/11366094 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166617 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Add some impl-side painting stub classes and APIsenne@chromium.org2012-11-089-0/+276
| | | | | | | | | BUG=155209 Review URL: https://chromiumcodereview.appspot.com/11265046 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166615 0039d316-1c4b-4281-b951-d872f2087c98
* Don't invert contentsDeviceTransform twice when rendering render passes.skaslev@chromium.org2012-11-083-10/+19
| | | | | | Review URL: https://chromiumcodereview.appspot.com/11361129 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166586 0039d316-1c4b-4281-b951-d872f2087c98
* Add touchEventHandlerRegion to Layer and LayerImplyusufo@chromium.org2012-11-083-0/+23
| | | | | | | | | | | | | These will be used to keep track of JavaScript touch event handler on the compositor thread and will be updated accordingly when there is a change involving adding/removing or changing the layout of the nodes that contain the touch event handlers. BUG=135818 Review URL: https://chromiumcodereview.appspot.com/11377013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166561 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Turn overdraw metrics on only when about:tracing is recording.danakj@chromium.org2012-11-074-36/+14
| | | | | | | | | | | | | | | | | | | | Now that we're in chromium, we can tell if about:tracing is enabled ot not! Turn on overdraw metrics, and their expensive computations, only when about:tracing is turned on. When we do turn them on, we don't want the performance characteristics of the system to suddenly change, or the tracing is not very meaningful! So, we track the number of pixels read, instead of written, for overdraw (which should mostly be the same with the new rasterScale feature). This computation is very cheap compared to the old one. TBR=jamesr BUG=119126 Relanding: https://codereview.chromium.org/11293143/ Review URL: https://codereview.chromium.org/11312129 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166521 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Rename PrioritizedTexture to PrioritizedResource.reveman@google.com2012-11-0736-475/+475
| | | | | | | | | | | | | | | | | | sed -e ' s/PrioritizedTexture/PrioritizedResource/g s/prioritized_texture/prioritized_resource/g s/PRIORITIZED_TEXTURE/PRIORITIZED_RESOURCE/g s/managedTexture/managedResource/g s/textureManager/resourceManager/g s/constentsTextureManager/constentsResourceManager/g ' BUG= TEST=cc_unittests Review URL: https://codereview.chromium.org/11369109 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166520 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 166464 - Turn overdraw metrics on only when about:tracing is recording.scottmg@google.com2012-11-074-14/+36
| | | | | | | | | | | | | | | | | | | | | | Now that we're in chromium, we can tell if about:tracing is enabled ot not! Turn on overdraw metrics, and their expensive computations, only when about:tracing is turned on. When we do turn them on, we don't want the performance characteristics of the system to suddenly change, or the tracing is not very meaningful! So, we track the number of pixels read, instead of written, for overdraw (which should mostly be the same with the new rasterScale feature). This computation is very cheap compared to the old one. R=jamesr BUG=119126 Review URL: https://codereview.chromium.org/11293143 TBR=danakj@chromium.org Review URL: https://codereview.chromium.org/11364132 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166477 0039d316-1c4b-4281-b951-d872f2087c98
* Turn overdraw metrics on only when about:tracing is recording.danakj@chromium.org2012-11-074-36/+14
| | | | | | | | | | | | | | | | | | | Now that we're in chromium, we can tell if about:tracing is enabled ot not! Turn on overdraw metrics, and their expensive computations, only when about:tracing is turned on. When we do turn them on, we don't want the performance characteristics of the system to suddenly change, or the tracing is not very meaningful! So, we track the number of pixels read, instead of written, for overdraw (which should mostly be the same with the new rasterScale feature). This computation is very cheap compared to the old one. R=jamesr BUG=119126 Review URL: https://codereview.chromium.org/11293143 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166464 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Fix nine patch layer resource management bugs.aelias@chromium.org2012-11-072-13/+8
| | | | | | | | | | | | This switches back to using if (m_resource) in pushPropertiesTo() since it may be called before setNeedsDisplay(). Also, switch to checking if resourceId == 0 instead of backingResourceIsDeleted() since that asserts it's only called on the impl thread. Review URL: https://chromiumcodereview.appspot.com/11377017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166399 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Sort the source file list of unittests.tfarina@chromium.org2012-11-071-11/+11
| | | | | | | | | | R=danakj@chromium.org, enne@chromium.org TBR=enne@chromium.org Review URL: https://chromiumcodereview.appspot.com/11312113 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166363 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Replace the WebCore::UnitBezier class with the SkUnitCubicInterp() ↵danakj@chromium.org2012-11-079-33/+125
| | | | | | | | | | | | | | | | | | | | | | | | | method from Skia. This method exists in Skia, but is not publicly consumable/linkable with a component build. Skia will expose this (or a similar) method through a proper public API, and we should use it. But in the meantime, we make a copy of the method in timing_function.cc, and use it there in place of WebCore's UnitBezier class. Tests: cc_unittests:TimingFunctionTest.CubicBezierTimingFunction This test compares the output of the timing function against baseline values recorded with WebCore's UnitBezier class. If new methods are able to come closer to those values, we should decrease the epsilon used in the test accordingly. R=jamesr BUG=147395 Review URL: https://chromiumcodereview.appspot.com/11359077 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166362 0039d316-1c4b-4281-b951-d872f2087c98
* LayerImpl::tryScroll must convert its content-space point to layer space ↵danakj@chromium.org2012-11-072-5/+10
| | | | | | | | | | | | | | | | | | | | | | | | | before comparing to the nonFastScrollableRegion. The hit test resulting point that the tryScroll() method gets is in content space, since it is the result of mapping via the inverse screenSpaceTransform. However, the nonFastScrollableRegion is in layer space, so it should not compare the point against the region directly. We add a conversion from content to layer space before doing the test. This is now covered by the following tests. Because the layer is given a contentsScale, the tests fail without the above change made to tryScroll. Tests: cc_unittests:LayerTreeHostImplTest.nonFastScrollableRegionBasic cc_unittests:LayerTreeHostImplTest.nonFastScrollableRegionWithOffset R=enne BUG=159676 Review URL: https://chromiumcodereview.appspot.com/11377006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166353 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Disable partial resource updates on Android.reveman@chromium.org2012-11-071-0/+4
| | | | | | | | | | | | This makes partialTextureUpdatesMax constant 0 when building for OS_ANDROID. BUG=156945 TEST=manual Review URL: https://chromiumcodereview.appspot.com/11347022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166347 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Maximize pending updates.reveman@chromium.org2012-11-063-33/+69
| | | | | | | | | | | | | | This makes the resource update controller maintain a maximum number of pending updates. This keeps our pipeline better filled without theoretically increasing the risk that we delay drawing at vsync tick. BUG=145825 TEST=cc_unittests and manual testing Review URL: https://chromiumcodereview.appspot.com/11347019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166298 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-30 03:47:35 +0000