- 19 Feb, 2015 39 commits
-
-
alancutter authored
This change makes tools/perf/page_sets/tough_animation_cases/resources/perftesthelper.js consistent with the Chromium Javascript style guide: - Fixed indentation - Added missing semicolon - Renamed file to be underscore separated Review URL: https://codereview.chromium.org/927583005 Cr-Commit-Position: refs/heads/master@{#316965}
-
tbansal authored
This change ensures that if a QUIC proxy is unreachable, then it is marked as bad. Allows chrome to retry the request with the next proxy instead of showing ERR_QUIC_PROTOCOL to user. BUG=459426 Review URL: https://codereview.chromium.org/936243002 Cr-Commit-Position: refs/heads/master@{#316964}
-
tommycli authored
BUG=458687, 403800 Review URL: https://codereview.chromium.org/929483004 Cr-Commit-Position: refs/heads/master@{#316963}
-
blink-deps-roller authored
Summary of changes available at: https://chromium.googlesource.com/chromium/blink/+log/830d38e..37a8479 TBR=yhirano@chromium.org,kbr@chromium.org Review URL: https://codereview.chromium.org/939843002 Cr-Commit-Position: refs/heads/master@{#316962}
-
creis authored
BUG=426953 TEST=See bug for repro steps. Review URL: https://codereview.chromium.org/913223009 Cr-Commit-Position: refs/heads/master@{#316961}
-
dfalcantara authored
Also deletes a bunch of comments that no longer apply and need to be rewritten. BUG=457413 Review URL: https://codereview.chromium.org/932263002 Cr-Commit-Position: refs/heads/master@{#316960}
-
anthonyvd authored
This is the first step in removing the flag entirely. BUG=457462 Review URL: https://codereview.chromium.org/931233004 Cr-Commit-Position: refs/heads/master@{#316959}
-
tbarzic authored
Moves creation of conversion_settings and bitmap_settings needed by PWGRasterConverter::Start to a place usable by code for handling extension printers. This will enable extension printer handler to reuse the code when converting pdf documents to PWG raster data. BUG=408772 TEST=existing tests Review URL: https://codereview.chromium.org/935673004 Cr-Commit-Position: refs/heads/master@{#316958}
-
raymes authored
The PDF viewer has 2 plugins associated with it. These are grouped correctly for Google Chrome but not for Chromium. This groups these plugins correctly for Chromium by updating the plugin metadata. BUG=459113 Review URL: https://codereview.chromium.org/931063002 Cr-Commit-Position: refs/heads/master@{#316957}
-
qinmin authored
SharedPreference.edit() creates a new editor. So calling this method twice creates 2 different editors. And the apply() call from the 2nd editor has no effect on the first editor. BUG=459403 Review URL: https://codereview.chromium.org/930303003 Cr-Commit-Position: refs/heads/master@{#316956}
-
enne authored
Property trees don't calculate lcd text settings on the main thread, so to move to them, these calculations need to move to the compositor thread. There's nothing tied to the main thread, other than only changing lcd text during a commit. This restriction avoids the pitfall of tile versions (i.e. changing out content in place with different settings) by only changing content and invalidating during a commit, which already waits for rasterization to occur before displaying that content. That restriction is satisfied by only updating lcd text on picture layers during an update on the sync tree on new frame numbers. Review URL: https://codereview.chromium.org/913203006 Cr-Commit-Position: refs/heads/master@{#316955}
-
mukai authored
- Usually, logical first segment should appear in the first line when multi-lined. This is the reported bug as crbug.com/458219 Therefore, TextRunHarfBuzz should be added to the line breaker in the logical order. - The segment order in a line is assumed as visual order, therefore it needs to be sorted. - Modified the test expectations which support this behavior. - Added new test cases to verify where exactly the segment is drawn. BUG=458219 R=msw@chromium.org, ckocagil@chromium.org TEST=gfx_unittests Review URL: https://codereview.chromium.org/924773002 Cr-Commit-Position: refs/heads/master@{#316954}
-
mgiuca authored
This means the grey text under the title, which usually explains what type the result is (e.g., "Google Search" or "Chrome Web Store"). BUG=450644 Review URL: https://codereview.chromium.org/935523002 Cr-Commit-Position: refs/heads/master@{#316953}
-
sergeyu authored
Clipboard is single-threaded, so Stop() is not useful there. Review URL: https://codereview.chromium.org/930403002 Cr-Commit-Position: refs/heads/master@{#316952}
-
pedrosimonetti authored
BUG=458379 Review URL: https://codereview.chromium.org/925733002 Cr-Commit-Position: refs/heads/master@{#316951}
-
dtseng authored
Previous attempts: https://codereview.chromium.org/880063002 https://codereview.chromium.org/895623003/ https://codereview.chromium.org/890013006/ https://codereview.chromium.org/907973004/ This latest attempt removes the logic that reloads ChromeVox at the beginning of a test. Locally, under extremely heavy load, tests progressively ran slowe. The same copy of a test ran 1 second slower than a previous copy. Ultimately, this led to a timeout. With the above change, this no longer occurs and hopefully fixes the flakeyness. Change is located in chromevox_e2e_test_base.js. TBR=dmazzoni@chromium.org Review URL: https://codereview.chromium.org/940763002 Cr-Commit-Position: refs/heads/master@{#316950}
-
vmiura authored
By defaulting Threaded GPU Rasterization to ON I inadvertently disabled using more than 1 raster thread for Software rasterization everywhere. Fixing so IsThreadedGpuRasterizationEnabled() is only on if Gpu rasterization is enabled or forced, so this will currently only be on for Android. We'll need a better way to support multiple raster worker threads to turn on GPU rasterization on desktops, or to support multiple render threads on Android. BUG=454500 BUG=459760 Review URL: https://codereview.chromium.org/941443002 Cr-Commit-Position: refs/heads/master@{#316949}
-
apacible authored
Example: for "chrome-extension://extensionid/page.html", Currently, the src would be set as: "chrome-extension://extensionid/page.html". With the change, the src would be set as: "page.html". BUG=459680 Review URL: https://codereview.chromium.org/936223002 Cr-Commit-Position: refs/heads/master@{#316948}
-
mgiuca authored
The new assets have correct colour contrast and more closely match the Material Design spec. Affects both the classic and experimental launcher. The following assets were replaced: - Microphone (hotword enabled and disabled states). - Back button. - Download progress bar. BUG=457979,456953 TBR=oshima@chromium.org Review URL: https://codereview.chromium.org/931483004 Cr-Commit-Position: refs/heads/master@{#316947}
-
chirantan authored
New chrome os devices are going to make more frequent use of the dark resume state - a hybrid power state where several hardware devices are left off to save power. One of these is the display. Unfortunately this creates issues with chrome, which believes that the display is on and attempts to render things to the screen. These calls fail in the kernel and trigger a logical memory leak in the error handling code in the GPU process. In order to make this interaction more robust, have chrome stop sending rendering requests at suspend time and restart them at resume time. There are a few things to watch out for here. If the user has requested that the screen be locked at suspend time then rendering cannot be stopped until the screen locker is visible. Otherwise the contents of the user's screen will be visible at resume time, which is a security issue. Additionally, the suspend must be delayed until any pending requests have been handled by the GPU process to prevent a race where the system suspends before all requests have been processed and they end up being processed when the system later enters dark resume, triggering the memory leak mentioned in the previous paragraph. BUG=chrome-os-partner:35699 Review URL: https://codereview.chromium.org/910393002 Cr-Commit-Position: refs/heads/master@{#316946}
-
https://codereview.chromium.org/938853002dougk authored
Address comments of RCH BUG=none Review URL: https://codereview.chromium.org/934383002 Cr-Commit-Position: refs/heads/master@{#316945}
-
ddorwin authored
This is temporary until we can determine a permanent solution. This cannot be implemented at a lower level because the lower levels do not know which version of EME is being used. BUG=394926 Review URL: https://codereview.chromium.org/936653004 Cr-Commit-Position: refs/heads/master@{#316944}
-
creis authored
This will be used to track session history items for subframes. For now, each NavigationEntry owns a single one for its main frame. BUG=236848 TEST=No behavior change. Review URL: https://codereview.chromium.org/931333004 Cr-Commit-Position: refs/heads/master@{#316943}
-
newt authored
The new accent color matches the rest of the app. BUG=459699 Review URL: https://codereview.chromium.org/941513002 Cr-Commit-Position: refs/heads/master@{#316942}
-
nednguyen authored
BUG=439497 Review URL: https://codereview.chromium.org/938743002 Cr-Commit-Position: refs/heads/master@{#316941}
-
danakj authored
This eliminates one use of TextureUploader via ResourceProvider::SetPixels. The PICTURE_PILE_MODE is renamed to OOM_MODE which more accurately describes what it is, and OOM tiles are displayed in red again instead of gray (something that changed with impl-side-painting). R=enne BUG=454575 Review URL: https://codereview.chromium.org/941433002 Cr-Commit-Position: refs/heads/master@{#316940}
-
reillyg authored
Avoid possibly long blocking times in the Windows SetupDi function calls made to enumerate devices by offloading to the FILE thread. Now that we can be sure that a stray request to the device won't block the UI additional calls to get the device's product and serial number strings can be made. BUG=457899 Review URL: https://codereview.chromium.org/936603003 Cr-Commit-Position: refs/heads/master@{#316939}
-
thestig authored
Also convert FormStructure::GetFieldTypePredictions() to return its data instead of using an out parameter. Review URL: https://codereview.chromium.org/934863003 Cr-Commit-Position: refs/heads/master@{#316938}
-
zmo authored
The current mechanism is to clean all cache, which is very misleading. Everytime we call LinkProgram, we simply delete the Program in the map, getting rid of all cahces, and create a new Program. BUG=429053 TEST=gpu_unittests R=bajones@chromium.org Review URL: https://codereview.chromium.org/933393003 Cr-Commit-Position: refs/heads/master@{#316937}
-
dfalcantara authored
DEPENDENT on 914813002 * Combines app_banner_metrics_ids.*, app_banner_utilities.*, and app_banner_metrics_id_list.* into the app_banner_metrics.* files. * Gets rid of the Java-side metrics because we can control and react to them entirely from native-side calls now. * Updates the histograms accordingly. BUG=457416 TBR=thakis Review URL: https://codereview.chromium.org/929533002 Cr-Commit-Position: refs/heads/master@{#316936}
-
palmer authored
BUG=415689 Review URL: https://codereview.chromium.org/580233002 Cr-Commit-Position: refs/heads/master@{#316935}
-
ccameron authored
This was reverted due to high crash rates on 10.10.2 (where we don't full crash reports). This was tested on branch and didn't affect the crash rate. The next step is to forward the event to the renderer. BUG=452592 Review URL: https://codereview.chromium.org/940733002 Cr-Commit-Position: refs/heads/master@{#316934}
-
sergeyu authored
Many ClientSession unittests assume that the first video frame always contains video dimensions. When running under valgrind the keep-alive timer may fire before the first video frame is sent and this breaks the tests. Fixed VideoFramePump to start sending keep-alive messages only after the first real frame is sent. Also made the keep-alive timer non-repeating. This ensures that the pump doesn't try sending a keep-alive message until the previous one has been sent. BUG=458691 Review URL: https://codereview.chromium.org/936553003 Cr-Commit-Position: refs/heads/master@{#316933}
-
anandc authored
Start running connect-to-localhost and connection-alive-after-focus-lost tests for v2 web-app on Linux. Also, reactivating v2 web-app Auth test on Linux, now that http://crbug/447778 has been fixed. BUG= Review URL: https://codereview.chromium.org/941493002 Cr-Commit-Position: refs/heads/master@{#316932}
-
twellington authored
(Temporarily) copy app compat thumb drawables to chrome/android/java/res. These were missed in the original CL to fix the app compat switch thumb not always being drawn (crbug.com/455327). BUG=459782 Review URL: https://codereview.chromium.org/937903002 Cr-Commit-Position: refs/heads/master@{#316931}
-
ddorwin authored
BUG=459400 Review URL: https://codereview.chromium.org/930413003 Cr-Commit-Position: refs/heads/master@{#316930}
-
rvargas authored
BUG=417532 Review URL: https://codereview.chromium.org/927443004 Cr-Commit-Position: refs/heads/master@{#316929}
-
thestig authored
BUG=405305 Review URL: https://codereview.chromium.org/927483002 Cr-Commit-Position: refs/heads/master@{#316928}
-
rdevlin.cronin authored
BUG=459649 TBR=calamity@chromium.org Review URL: https://codereview.chromium.org/939813002 Cr-Commit-Position: refs/heads/master@{#316927}
-
- 18 Feb, 2015 1 commit
-
-
tsergeant authored
Adds an ellipsis to the 'Create shortcuts' and 'Remove' buttons, which both require additional user input. BUG=448359 Review URL: https://codereview.chromium.org/926993002 Cr-Commit-Position: refs/heads/master@{#316926}
-