- 14 Oct, 2014 27 commits
-
-
achuith authored
* Add enrollment status to proto * Remove stages not handled by HostPairingController, and ControllerPairingController. * UpdateScreen sends update status via remora_controller. * EnrollmentScreen sends enrollment status via remora_controller. * Remove auth_token_ from EnrollmentScreen. * Rename to shark_controller and remora_controller in WizardController. * Remove get_initial_status_ from BluetoothControllerPairingController. Review URL: https://codereview.chromium.org/652743003 Cr-Commit-Position: refs/heads/master@{#299422}
-
aelias authored
r297913 introduced the bug that if another activation happens during a page scale animation, it's clobbered by a null pointer. Only copy into LTHI::page_scale_animation_ when the LTI has an instance of it. NOTRY=true BUG=419450 Review URL: https://codereview.chromium.org/650353003 Cr-Commit-Position: refs/heads/master@{#299421}
-
yoichio authored
Revert of [Easy Unlock] Port the BluetoothConnectionFinder class to native code. (patchset #4 id:320001 of https://codereview.chromium.org/633253002/) Reason for revert: Causes compile failure on mac: http://build.chromium.org/p/chromium.mac/builders/Mac%20Builder%20%28dbg%29/builds/75518 Original issue's description: > [Easy Unlock] Port the BluetoothConnectionFinder class to native code. > > A couple of pieces are left as TODOs for future CLs: > * Porting the "seek device by Bluetooth address" feature. > * Wiring up a screen lock state accessor. > > BUG=420946 > TEST=components_unittests > R=tengs@chromium.org > > Committed: https://crrev.com/ac4df1c4df6fdc7c771eb0bdeb15dbd6f2dbb98c > Cr-Commit-Position: refs/heads/master@{#299415} TBR=tengs@chromium.org,isherman@chromium.org NOTREECHECKS=true NOTRY=true BUG=420946 Review URL: https://codereview.chromium.org/651073002 Cr-Commit-Position: refs/heads/master@{#299420}
-
viettrungluu authored
For every two problems that C++11 causes, it fixes at least one. R=thestig@chromium.org,tsepez@chromium.org BUG=423134 Review URL: https://codereview.chromium.org/647753003 Cr-Commit-Position: refs/heads/master@{#299419}
-
mostynb authored
R=jochen@chromium.org,falken@chromium.org BUG=417463 Review URL: https://codereview.chromium.org/653593003 Cr-Commit-Position: refs/heads/master@{#299418}
-
alancutter authored
This adds several performance tests for CSS Transitions initiated in various ways. BUG=309981,421733 Review URL: https://codereview.chromium.org/399393002 Cr-Commit-Position: refs/heads/master@{#299417}
-
boliu authored
* Remove unneeded includes, using, etc * Use base::debug::ConvertableToTraceFormat * Fix up some comments * Make const a global var BUG= Review URL: https://codereview.chromium.org/649683004 Cr-Commit-Position: refs/heads/master@{#299416}
-
isherman authored
A couple of pieces are left as TODOs for future CLs: * Porting the "seek device by Bluetooth address" feature. * Wiring up a screen lock state accessor. BUG=420946 TEST=components_unittests R=tengs@chromium.org Review URL: https://codereview.chromium.org/633253002 Cr-Commit-Position: refs/heads/master@{#299415}
-
shuchen authored
This CL adds a new 'noUnderline' enum value in the segment style in chrome.input.ime.setComposition(). BUG=407576 TEST=Verified on linux_chromeos with a test IME extension. Review URL: https://codereview.chromium.org/639103003 Cr-Commit-Position: refs/heads/master@{#299414}
-
abarth authored
Previously, we just used ugly numbered names as the local names for modules in JavaScript. Now we try to use a meaningful name based on the name of the module. There shouldn't be any behavior change. R=hansmuller@chromium.org Review URL: https://codereview.chromium.org/653793002 Cr-Commit-Position: refs/heads/master@{#299413}
-
pkasting authored
The only change since the previous revision is unconditionally using static_assert in third_party/macros.h. This gets rid of the old code that used ALLOW_UNUSED and will ensure there are no conflicts of any kind as I change how the version of ALLOW_UNUSED in Chromium works. BUG=81439 TEST=none TBR=jam Review URL: https://codereview.chromium.org/654783003 Cr-Commit-Position: refs/heads/master@{#299412}
-
estade authored
BUG=231160 Review URL: https://codereview.chromium.org/650293002 Cr-Commit-Position: refs/heads/master@{#299411}
-
reillyg authored
Update the perf expectations for nacl_helper-data to reflect the binary size improvements from the recent ICU work. BUG= TBR=maruel@chromium.org,govind@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/655683002 Cr-Commit-Position: refs/heads/master@{#299410}
-
pkasting authored
BUG=81439 TEST=none Review URL: https://codereview.chromium.org/656663002 Cr-Commit-Position: refs/heads/master@{#299409}
-
xiyuan authored
Tighten finch check a bit so that the missing trial is treated as disable. BUG=423016 Review URL: https://codereview.chromium.org/649223003 Cr-Commit-Position: refs/heads/master@{#299408}
-
estade authored
R=felt@chromium.org BUG=none Review URL: https://codereview.chromium.org/656523002 Cr-Commit-Position: refs/heads/master@{#299407}
-
sungmann.cho authored
Currently, the lint warns at: AccountsAdapter.java:29 Unconditional layout inflation from view adapter: Should use View Holder pattern (use recycled view passed into this method as the second parameter) for smoother scrolling: ViewHolder [warning] This CL fixes the above lint error. BUG=327768 Review URL: https://codereview.chromium.org/628133003 Cr-Commit-Position: refs/heads/master@{#299406}
-
blink-deps-roller authored
Summary of changes available at: https://chromium.googlesource.com/chromium/blink/+log/ef3851c..4c8283b TBR=caseq@chromium.org,apavlov@chromium.org,cbiesinger@chromium.org Review URL: https://codereview.chromium.org/653783002 Cr-Commit-Position: refs/heads/master@{#299405}
-
rdevlin.cronin authored
BUG=357204 Review URL: https://codereview.chromium.org/641043003 Cr-Commit-Position: refs/heads/master@{#299404}
-
tonyg authored
Now we only try to calculate application_energy_consumption when we actually have a known quiescent power draw. This means we'll still output it on tab_switching, but not on page cycler. That should fix errors like this: http://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf/builds/2187/steps/page_cycler.morejs/logs/stdio BUG= Review URL: https://codereview.chromium.org/649903003 Cr-Commit-Position: refs/heads/master@{#299403}
-
wtc authored
R=agl@chromium.org BUG= Review URL: https://codereview.chromium.org/652953002 Cr-Commit-Position: refs/heads/master@{#299402}
-
thestig authored
BUG=395172 NOTRY=true TBR=bruening@chromium.org Review URL: https://codereview.chromium.org/652083002 Cr-Commit-Position: refs/heads/master@{#299401}
-
pkasting authored
an explicit "!= 0". BUG=81439 TEST=none Review URL: https://codereview.chromium.org/650303003 Cr-Commit-Position: refs/heads/master@{#299400}
-
zmo authored
BUG=421695 TEST=gpu_unittests, webgl_conformance_tests R=bajones@chromium.org Review URL: https://codereview.chromium.org/656613002 Cr-Commit-Position: refs/heads/master@{#299399}
-
rtenneti authored
+ Formatting/indentation changes. R=rch@chromium.org Review URL: https://codereview.chromium.org/651993003 Cr-Commit-Position: refs/heads/master@{#299398}
-
vadimt authored
Mechanical change that adds instrumentation required to locate the source of jankiness (i.e. a long-running fragment of code executed as a part of the task that causes jank) in the code. See the bug for details on what kind of jank we are after. A number of similar CLs were landed, and none of them caused issues. The code of the instrumentation is highly optimized and is not expected to affect performance. The code simply creates a diagnostic task which is identical to ones created by PostTask or IPC message handlers. Landing as TBR since this is a mechanical, safe and temporary change. This CL instruments callbacks invoked from the last "PostOrRunCallback" call in "SSLClientSocketNSS::Core::DoReadCallback". BUG=418183 TBR=asanka@chromium.org, zea@chromium.org Review URL: https://codereview.chromium.org/646273003 Cr-Commit-Position: refs/heads/master@{#299397}
-
pdr authored
Revert of Enable the Rightware Browsermark benchmark (patchset #1 id:1 of https://codereview.chromium.org/649283002/) Reason for revert: Temporarily disable the Rightware Browsermark benchmark Original issue's description: > Enable the Rightware Browsermark benchmark > > This patch un-disables the rightware browsermark benchmark. Manually > testing shows this finishes in under 5m on a Nexus 5. > > BUG=423018 > > Committed: https://crrev.com/6c816144b656046b41cd0cc3bce167e9a3a9febc > Cr-Commit-Position: refs/heads/master@{#299369} TBR=qyearsley@chromium.org,wangxianzhu@chromium.org,tonyg@chromium.org NOTREECHECKS=true NOTRY=true BUG=423018 Review URL: https://codereview.chromium.org/649353003 Cr-Commit-Position: refs/heads/master@{#299396}
-
- 13 Oct, 2014 13 commits
-
-
jbauman authored
WGL needs to create a window and should pump its message loop, so use a UI message loop. BUG=273220 Review URL: https://codereview.chromium.org/643373002 Cr-Commit-Position: refs/heads/master@{#299395}
-
amistry authored
The audio_client.js content script is copied from the existing hotword_helper extesion, with the only change being the hotword extension ID to point to this new extension. BUG=397019 Review URL: https://codereview.chromium.org/600523004 Cr-Commit-Position: refs/heads/master@{#299394}
-
skia-deps-roller authored
Summary of changes available at: https://chromium.googlesource.com/skia/+log/6c07907..07894c4 CQ_EXTRA_TRYBOTS=tryserver.blink:linux_blink_rel,linux_blink_dbg TBR=rmistry@google.com Review URL: https://codereview.chromium.org/656553002 Cr-Commit-Position: refs/heads/master@{#299393}
-
tapted authored
TransformPathForFeature in child_process_host_impl.cc expects to find `Chromium Helper XX` inside the .app bundle, but views_examples_with_content_exe is a standalone executable. The example app doesn't need plugins so this CL disables plugin discovery to avoid: Check failed: kMacOSName == macos_path.BaseName().value() (MacOS vs. Debug) This occurs when particular pages are loaded in the WebView example, triggered via content::PluginLoaderPosix::LoadPluginsInternal(). The change is made in views_content_client, which affects app_list_demo and views_examples_with_content_exe. BUG=395507 Review URL: https://codereview.chromium.org/655433002 Cr-Commit-Position: refs/heads/master@{#299392}
-
andresantoso authored
Revert of Mac: Update sheet position when bookmark bar is shown or hidden. (patchset #1 id:1 of https://codereview.chromium.org/502413004/) Reason for revert: Broke certificate info positioning when switching tabs (http://crbug.com/419371). I will need to come up with a better fix for this, but it looks complicated and that bug is a M39 stable blocker so reverting this first. Original issue's description: > Mac: Update sheet position when bookmark bar is shown or hidden. > > In r272421, I changed sheet repositioning on window resize to be based on > NSWindowDidResizeNotification instead of NSViewFrameDidChangeNotification > because it tracks window resizing much more smoothly. > > That caused this problem where if the browser window is vertically maximized > (or is in fullscreen), the window size does not change when the bookmark bar > is shown or hidden. > > The old code has a different bug however. If the browser window is not > vertically maximized, showing or hiding the bookmark bar does not change the > browser content view's frame. It moves up or down to follow the window resize > but its frame relative to its superview remains the same. > > I settled for adding code to explicitly update the sheet's position when the > bookmark bar is shown or hidden. > > BUG=407509 > > Committed: https://crrev.com/5648b809d1c50e3de754b96abe7cf2b60150ff4d > Cr-Commit-Position: refs/heads/master@{#292421} TBR=avi@chromium.org BUG=407509 Review URL: https://codereview.chromium.org/653733002 Cr-Commit-Position: refs/heads/master@{#299391}
-
jamuraa authored
Also use a new method for callback chaining, which is slightly less flexible but much less "callback hell". BUG=377232 R=armansito@chromium.org Review URL: https://codereview.chromium.org/628983003 Cr-Commit-Position: refs/heads/master@{#299390}
-
vadimt authored
Mechanical change that adds instrumentation required to locate the source of jankiness (i.e. a long-running fragment of code executed as a part of the task that causes jank) in the code. See the bug for details on what kind of jank we are after. A number of similar CLs were landed, and none of them caused issues. The code of the instrumentation is highly optimized and is not expected to affect performance. The code simply creates a diagnostic task which is identical to ones created by PostTask or IPC message handlers. Landing as TBR since this is a mechanical, safe and temporary change. This CL specifically instruments some presumably most popular callbacks invoked by “callback.Run(result);” line in TCPClientSocket::DidCompleteReadWrite. BUG=418183 TBR=asanka@chromium.org Review URL: https://codereview.chromium.org/652853002 Cr-Commit-Position: refs/heads/master@{#299389}
-
jbauman authored
This causes a deadlock, so it's not usable. Getting rid of the window at least allows --in-process-gpu to work. BUG=273220 Review URL: https://codereview.chromium.org/649863002 Cr-Commit-Position: refs/heads/master@{#299388}
-
zmo authored
BUG=415688 TEST=gpu_unittests, webgl_conformance_tests R=kbr@chromium.org,bajones@chromium.org Review URL: https://codereview.chromium.org/651543003 Cr-Commit-Position: refs/heads/master@{#299387}
-
vmpstr authored
In smoothness takes priority mode, we should ensure to return tiles that are required for activation sooner than eventually bin. The reason for this is that we don't want to starve activation and the prepainting required for smoothness should already be covered by the soon bin. Additionally, we have to ensure not to mark these tiles as violating memory policy, since required for activation tiles need special treatment (unfortunately). The reason for this is that activation is currently tied to updating our recordings and smoothness mode would otherwise starve activation even if we're past the recording region. BUG=422819 R=reveman Review URL: https://codereview.chromium.org/651503004 Cr-Commit-Position: refs/heads/master@{#299386}
-
gunsch authored
Motivation: * chromecast/service/ directory had interplay with chromecast/shell/browser code, since the service is all run in the browser process and mildly coupled (involves starting WebContents instances, etc,). Made more sense for chromecast/service to live in chromecast/shell/browser. * chromecast/shell/ directory is needless hierarchy, since the entire chromecast/ directory represents the Chromecast content-embedder. Highlights: * chromecast/shell/{app,browser,common,renderer} --> chromecast/* * chromecast/shell/browser/resources --> chromecast/app/resources * chromecast/shell/settings --> chromecast/app/resources * chromecast/shell/android --> chromecast/browser/android * chromecast/metrics --> chromecast/browser/metrics * chromecast/service --> chromecast/browser/service R=lcwu@chromium.org,gusfernandez@chromium.org,byungchul@chromium.org TBR=xhwang@chromium.org,asvitkine@chromium.org,thestig@chromium.org,jam@chromium.org,yfriedman@chromium.org BUG=None Review URL: https://codereview.chromium.org/638803002 Cr-Commit-Position: refs/heads/master@{#299385}
-
bokan authored
This change adjusts the scroll bubbling logic in LayerTreeHostImpl so that outer viewport layer scrolls affect the top controls. Additionally, the outer viewport's size is adjusted to match the inner viewport's aspect ratio until a resize occurs. Blink side: https://codereview.chromium.org/643473002 BUG=364109 Review URL: https://codereview.chromium.org/641873003 Cr-Commit-Position: refs/heads/master@{#299384}
-
blink-deps-roller authored
Summary of changes available at: https://chromium.googlesource.com/chromium/blink/+log/c5733ed..ef3851c TBR=caseq@chromium.org,apavlov@chromium.org,cbiesinger@chromium.org Review URL: https://codereview.chromium.org/656543004 Cr-Commit-Position: refs/heads/master@{#299383}
-