- 06 Apr, 2013 37 commits
-
-
dcheng@chromium.org authored
BUG=171111 Review URL: https://codereview.chromium.org/13482006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192700 0039d316-1c4b-4281-b951-d872f2087c98
-
thakis@chromium.org authored
BUG=none TBR=dcheng Review URL: https://codereview.chromium.org/13482008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192697 0039d316-1c4b-4281-b951-d872f2087c98
-
dhollowa@chromium.org authored
Adds additional suppressions for leak in TiledLayer::Update, started at the same time as leaks in ScreenshotTakerTest, so am marking this against the same CL/Bug. BUG=227271 TEST=ScreenshotTakerTest::TakeScreenshot TBR=sschmitz@chromium.org Review URL: https://codereview.chromium.org/13710003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192692 0039d316-1c4b-4281-b951-d872f2087c98
-
erg@chromium.org authored
This makes text in the omnibox dropdown visible again on linux_aura. BUG=130810 Review URL: https://chromiumcodereview.appspot.com/13722014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192690 0039d316-1c4b-4281-b951-d872f2087c98
-
mgiuca@chromium.org authored
This is a better description of the operation, since it is fuzzy rather than a direct lookup. BUG=189137 Review URL: https://chromiumcodereview.appspot.com/13713002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192689 0039d316-1c4b-4281-b951-d872f2087c98
-
varunjain@chromium.org authored
This is mostly a copy of https://chromiumcodereview.appspot.com/12395010 which was reverted due to a regression (https://code.google.com/p/chromium/issues/detail?id=189100). I have attempted to fix that regression here. BUG=189100,179381 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=192525 Review URL: https://chromiumcodereview.appspot.com/12529012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192688 0039d316-1c4b-4281-b951-d872f2087c98
-
dhollowa@chromium.org authored
Adds suppressions for leaks in disk_cache::BackendIO. BUG=227301 TEST=Heapcheck goes green. TBR=dsinclair@chromium.org Review URL: https://codereview.chromium.org/13445008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192687 0039d316-1c4b-4281-b951-d872f2087c98
-
thestig@chromium.org authored
Storage Monitor: Remove MediaTransferProtocolDeviceObserverLinux::GetInstance() and access it only from StorageMonitor. Review URL: https://chromiumcodereview.appspot.com/13533009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192686 0039d316-1c4b-4281-b951-d872f2087c98
-
xhwang@chromium.org authored
TBR=scottmg@chromium.org BUG=227296 Review URL: https://codereview.chromium.org/13552006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192685 0039d316-1c4b-4281-b951-d872f2087c98
-
dhollowa@chromium.org authored
Adds suppressions for leaks in CompositingIOSurfaceTransformerTest.*. BUG=227278 TEST=CompositingIOSurfaceTransformerTest.* on Valgrind TBR=miu@chromium.org Review URL: https://codereview.chromium.org/13742003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192684 0039d316-1c4b-4281-b951-d872f2087c98
-
rlp@chromium.org authored
[Spellcheck] Record the number of words in the custom dictionary when the custom dictionary is loaded. This was removed during the refactor and needs to be put back in. BUG=226249 TEST=SpellcheckCustomDictionaryTest::RecordSizeStatsCorrectly Review URL: https://chromiumcodereview.appspot.com/13428008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192683 0039d316-1c4b-4281-b951-d872f2087c98
-
newt@chromium.org authored
content_browsertests were timing out on the Android FYI bots since it took more than 7 minutes to push the test files to the device. This extends the timeout to 20 minutes, as a stopgap until we can reduce the number of files that need to be pushed. BUG=138275 Review URL: https://chromiumcodereview.appspot.com/13674021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192682 0039d316-1c4b-4281-b951-d872f2087c98
-
beaudoin@chromium.org authored
BUG=155373 Review URL: https://chromiumcodereview.appspot.com/13727003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192681 0039d316-1c4b-4281-b951-d872f2087c98
-
sail@chromium.org authored
When on a search results page the bookmark bar should be shown. This was a regression from r189607. Fix was to hide the bookmark bar in MODE_SEARCH_RESULTS as well as MODE_SEARCH_SUGGESTIONS. BUG=225767 TEST= Added a regression test, BrowserWindowControllerTest.InstantSearchResultsMode. Ran Chrome in instant extended mode. Did a search and clicked on the results page. Verified that the bookmark bar stayed hidden. Review URL: https://chromiumcodereview.appspot.com/13726019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192680 0039d316-1c4b-4281-b951-d872f2087c98
-
jamiewalch@chromium.org authored
Apps v2 can't access window.localStorage, so the settings migration code throws an exception under apps v2. BUG=226488,134213 Review URL: https://chromiumcodereview.appspot.com/13601016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192679 0039d316-1c4b-4281-b951-d872f2087c98
-
skaslev@chromium.org authored
BUG=124671, 161008 NOTRY=true Review URL: https://chromiumcodereview.appspot.com/13042012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192678 0039d316-1c4b-4281-b951-d872f2087c98
-
dhollowa@chromium.org authored
Adds suppressions for leak in ScreenshotTakerTest. BUG=227271 TEST=ScreenshotTakerTest::TakeScreenshot R=sschmitz@chromium.org Review URL: https://codereview.chromium.org/13445006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192677 0039d316-1c4b-4281-b951-d872f2087c98
-
backer@chromium.org authored
We use it in compositor_unittests to have a faster refresh rate during test (when WGC3D is mocked out --- no hardware vsync). TEST=cc_unittests pass, compositor_unittests --ui-enable-threaded-compositing are faster Review URL: https://chromiumcodereview.appspot.com/13674006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192676 0039d316-1c4b-4281-b951-d872f2087c98
-
vmpstr@chromium.org authored
Drawing info now has everything it needs to calculate the contents_swizzled instead of it being set in TileManager in two spots. BUG=225804 Review URL: https://chromiumcodereview.appspot.com/13665003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192675 0039d316-1c4b-4281-b951-d872f2087c98
-
ccameron@chromium.org authored
TBR=nduca@chromium.org BUG= Review URL: https://chromiumcodereview.appspot.com/13655002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192674 0039d316-1c4b-4281-b951-d872f2087c98
-
acolwell@chromium.org authored
BUG=172688 Review URL: https://chromiumcodereview.appspot.com/13652012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192673 0039d316-1c4b-4281-b951-d872f2087c98
-
tomfinegan@chromium.org authored
Review URL: https://chromiumcodereview.appspot.com/13652011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192672 0039d316-1c4b-4281-b951-d872f2087c98
-
danakj@chromium.org authored
The compositor should tick and finish animations even if it is not drawing anything. It can not draw for various reasons: 1) The tab is backgrounded. 2) CanDraw() is false for any of its reasons. 3) PrepareToDraw() fails due to checkerboarding. 4) There is no damage on the screen to draw. Currently the problems are: - When backgrounded, the animations are ticked but their states are not updated. - When CanDraw() is false, we don't draw, and animations just stop ticking. - If we stop drawing when we damage the screen, we tick animations, but don't update animation state since this happens in DrawLayers(). To solve these problems, I've moved the animation control more explicitly out of LayerTreeHostImpl. The proxy already calls Animate(). Now it will also call UpdateAnimationState(). It always does this after calling Animate() regardless if drawing or not. Secondly, the missing UpdateAnimationState() call is added to the OnTimerTick for background animation ticking. We enable background ticking only when we change visibility, currently. But when CanDraw() is false, we don't draw and thus don't tick animations. So instead we add to LayerTreeHostImpl a UpdateBackgroundAnimateTicking() method. We call this always after calling Animate() since that can remove animations - it's something Animate() used to do. And we also call this: a) After a commit - this could add new animations, or change visibility. b) After changing CanDraw()'s state. However, when PrepareToDraw() is false, we do not want to start new animations so we let animations finish without starting new ones. This is verified by the LayerTreeHostAnimationTestCheckerboardDoesntStartAnimations test. This is covered by adding single-thread mode to all the animation unit tests (except those that call SetNeedsAnimate() which is not legal in single thread mode). Also by new tests: LayerTreeHostAnimationTestRunAnimationWhenNotCanDraw.RunSingleThread LayerTreeHostAnimationTestRunAnimationWhenNotCanDraw.RunMultiThread LayerTreeHostAnimationTestRunAnimationWhenNotVisible.RunSingleThread LayerTreeHostAnimationTestRunAnimationWhenNotVisible.RunMultiThread LayerTreeHostAnimationTestCheckerboardDoesntStartAnimations.RunMultiThread Added scheduler tests: SchedulerStateMachineTest.ReportIfNotDrawing SchedulerStateMachineTest.ReportIfNotDrawingFromAcquiredTextures R=ajuma@chromium.org BUG=222915 Review URL: https://chromiumcodereview.appspot.com/13613003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192671 0039d316-1c4b-4281-b951-d872f2087c98
-
justinlin@chromium.org authored
Add tracing for capture timestamps. BUG=225209 Review URL: https://chromiumcodereview.appspot.com/13554003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192670 0039d316-1c4b-4281-b951-d872f2087c98
-
raymes@chromium.org authored
TBR=brettw@chromium.org Review URL: https://chromiumcodereview.appspot.com/13004012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192669 0039d316-1c4b-4281-b951-d872f2087c98
-
sivachandra@chromium.org authored
This CL adds --auto-reconnect as an option to the provisioning script. This option is not being used. BUG=164180 Review URL: https://chromiumcodereview.appspot.com/13649010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192668 0039d316-1c4b-4281-b951-d872f2087c98
-
dbeam@chromium.org authored
issue somewhere (I'm sure). R=sky@chromium.org BUG=224259 Review URL: https://chromiumcodereview.appspot.com/13533021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192667 0039d316-1c4b-4281-b951-d872f2087c98
-
rlarocque@chromium.org authored
This change separates the tracking of what work needs to be done from the decision of when to do it. Prior to this change, SyncSessionJobs were owned either by Closures posted to the sync thread's message loop, or held temporarily in unscheduled_nudge_storage_, a member of the SyncScheduler. Following this change, there can be only two jobs in existence, and they will be referenced only by the scoped_ptr members of SyncScheduler named pending_nudge_job_ and pending_configure_job_. This change, along with some previous changes to the way we schedule tasks, makes it possible to simplify the job "saving" logic. Jobs with purpose == NUDGE are saved by assigning them to pending_nudge_job_ or coalescing them with the existing pending_nudge_job_. Jobs with purpose == CONFIGURE are never coalesced, and can be saved in the pending_configure_job_ member. These changes allow us to make SyncSessionJob::Clone() obsolete. The logic in ScheduleNudgeImpl() has been updated to take advantage of the fact that the pending job is much easier to find now. It should now be much better at coalescing its sources. In other words, there will be less scenarios where it can drop notification hints. However, there are still some cases in DecideOnJob() that may induce it to drop hints unnecessarily. The scheduling logic has been modified, too. We've removed support for the nudge while in an exponential backoff interval. This makes it possible to track the next wakeup time using a single timer, since the wakeup event will be one of: - The end of a throttled interval - An end-of-backoff-interval retry - A scheduled nudge and these scenarios are now mutually exclusive. BUG=175024 Review URL: https://chromiumcodereview.appspot.com/13422003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192666 0039d316-1c4b-4281-b951-d872f2087c98
-
cbiesinger@chromium.org authored
Webkit has supported unprefixed box-shadow since December 2010: http://peter.sh/2010/12/no-more-delete-unprefixed-box-shadows-and-a-have-happy-new-year/ BUG= Review URL: https://chromiumcodereview.appspot.com/12842013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192665 0039d316-1c4b-4281-b951-d872f2087c98
-
xiyuan@chromium.org authored
BUG=178469 Review URL: https://chromiumcodereview.appspot.com/13638012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192663 0039d316-1c4b-4281-b951-d872f2087c98
-
cjhopman@chromium.org authored
Currently, normal APKs and instrumentation APKs are both built using java_apk.gypi (which includes all kinds of new hotness). Native unittest APKs, though use apk_test.gypi and thus the complicated native_test_apk.xml and Android's Ant build.xml. That is bad. This change updates apk_test.gypi to include java_apk.gypi and so brings these two ways of building APKs into alignment. It also very slightly updates the configurability of java_apk.gypi and apk-package.xml. There are still a couple of targets in WebKit that use generate_native_test.py and native_test_apk.xml directly that need to be updated to use apk_test.gypi before those two scripts can be simplified/removed. BUG=158821 Review URL: https://chromiumcodereview.appspot.com/13564003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192662 0039d316-1c4b-4281-b951-d872f2087c98
-
backer@chromium.org authored
Check that a draw occured, rather than just that it was scheduled. Verify that CompositorDelegate is not called if compositing is threaded. BUG=173417 TEST=compositor_unittests --ui-enable-threaded-compositing Review URL: https://chromiumcodereview.appspot.com/13555004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192661 0039d316-1c4b-4281-b951-d872f2087c98
-
avi@chromium.org authored
BUG=196349 TEST=SecurityTest.NewOverflow and CallocOverflow should not fail as part of a long test run Review URL: https://chromiumcodereview.appspot.com/13529020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192660 0039d316-1c4b-4281-b951-d872f2087c98
-
ajuma@chromium.org authored
This makes ui::Layer use cc::Layer::SetPosition for setting its position, instead of baking its position into the transform that's set on the cc::Layer. This means that a change to a ui::Layer's bounds no longer affects the transform set on the cc::Layer, and hence bounds animations no longer conflict with threaded transform animations. BUG=170219,226326 Review URL: https://chromiumcodereview.appspot.com/13725015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192659 0039d316-1c4b-4281-b951-d872f2087c98
-
sebmarchand@chromium.org authored
Context: https://groups.google.com/a/chromium.org/forum/?fromgroups=#!topic/chromium-dev/1aTQc4fd-rk BUG= Review URL: https://chromiumcodereview.appspot.com/13529016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192658 0039d316-1c4b-4281-b951-d872f2087c98
-
cpu@chromium.org authored
See bug attached for screenshots The CL does two things: - Disables the resizer lock, so that UI bits can go ahead of content bits - Janks (blocks) the UI thread until the compositor has flushed / finished the pending commands. This makes the mis-draw way less, up to one frame behind, which at my regular mouse speed of 1.2 pixels / ms comes out to 20 pixels of whiteout. BUG=177115 TEST=none Review URL: https://codereview.chromium.org/13604007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192657 0039d316-1c4b-4281-b951-d872f2087c98
-
nileshagrawal@chromium.org authored
BUG=138275 Review URL: https://codereview.chromium.org/13533022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192656 0039d316-1c4b-4281-b951-d872f2087c98
-
- 05 Apr, 2013 3 commits
-
-
achuith@chromium.org authored
BUG=225911 TEST=manual + browser test ExtensionApi.AutotestPrivate Review URL: https://chromiumcodereview.appspot.com/13520005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192655 0039d316-1c4b-4281-b951-d872f2087c98
-
palmer@chromium.org authored
It should be crystal clear when, and why, pin validation is and is not performed. TEST=net_unittests; with an OFFICIAL_BUILD: can still connect to pinned sites, and https://pinningtest.appspot.com fails with net::ERR_SSL_PINNED_KEY_NOT_IN_CERT_CHAIN. Review URL: https://chromiumcodereview.appspot.com/13466020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192654 0039d316-1c4b-4281-b951-d872f2087c98
-
mostynb@opera.com authored
BUG=none Review URL: https://chromiumcodereview.appspot.com/13431003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192653 0039d316-1c4b-4281-b951-d872f2087c98
-