- 13 May, 2015 40 commits
-
-
sbc authored
Previously this was called --linux-only which was a little misleading since this flag is really used to detect when it running via the hooks. Review URL: https://codereview.chromium.org/1099003002 Cr-Commit-Position: refs/heads/master@{#329579}
-
xiyuan authored
BUG=449816 Review URL: https://codereview.chromium.org/1128683003 Cr-Commit-Position: refs/heads/master@{#329578}
-
michaelpg authored
BUG=485381 Review URL: https://codereview.chromium.org/1130113005 Cr-Commit-Position: refs/heads/master@{#329577}
-
blink-deps-roller authored
Summary of changes available at: https://chromium.googlesource.com/chromium/blink/+log/76a74c1..69b829f TBR=dpranke@chromium.org,alancutter@chromium.org Review URL: https://codereview.chromium.org/1138373003 Cr-Commit-Position: refs/heads/master@{#329576}
-
chrome-tpm authored
Cr-Commit-Position: refs/heads/master@{#329575}
-
mgiuca authored
This is used to rank apps and webstore results. This should not (really) affect the relative ranking of any results, only the absolute scores that they are assigned internally. However, this will be relevant in the future when we start comparing scores of different types of results against each other. The algorithm (used to score app and webstore results) now has a different tapering formula, designed to reach a higher score with fewer keystrokes. Previously, it was based on the percentage of the full title you had typed (which unfairly de-prioritized apps with long titles, such as "Google Keep - notes and lists"). Now, it has an exponential curve, so you get a reasonably high score with just a few letters matched, and then it tapers off, approaching 1.0 as you type more letters. BUG=422610 Review URL: https://codereview.chromium.org/1138193002 Cr-Commit-Position: refs/heads/master@{#329574}
-
yawano authored
BUG=486236 TEST=manually tested. Review URL: https://codereview.chromium.org/1141563002 Cr-Commit-Position: refs/heads/master@{#329573}
-
apacible authored
There was no icon specified for the <paper-icon-button> for closing the WebUI. This adds the "close" icon for this <paper-icon-button>. Review URL: https://codereview.chromium.org/1139663003 Cr-Commit-Position: refs/heads/master@{#329572}
-
kalman authored
The first is 1be16298: "Clear the onMessage and onDisconnect listeners when their Extension Port is destroyed." which was a fix to the original patch. The second, original patch is 32b3a84b: "Move the Extension Port implementation out of messaging.js into its own file port.js." This is the key patch, which has caused no end of trouble. The goal was noble: to fix the myriad of bugs which messaging has due to being written in JS not C++. It appears that the moral of the story is: this is impossible, and the hole we've dug in over the last 5 years cannot be recovered from (without a complete rewrite, I suppose). The last .5 of a patch was one of the tests added in b9dca054 which will no longer pass. BUG=486715,477323,475536 R=rockot@chromium.org Review URL: https://codereview.chromium.org/1131043003 Cr-Commit-Position: refs/heads/master@{#329571}
-
michaelpg authored
BUG=485381 NOTRY=true Review URL: https://codereview.chromium.org/1134553006 Cr-Commit-Position: refs/heads/master@{#329570}
-
jlklein authored
BUG=485381 Review URL: https://codereview.chromium.org/1137103002 Cr-Commit-Position: refs/heads/master@{#329569}
-
jlklein authored
BUG=485381 Review URL: https://codereview.chromium.org/1125343005 Cr-Commit-Position: refs/heads/master@{#329568}
-
oshima authored
This is a regression in https://codereview.chromium.org/1114633002c BUG=485832 TEST=covered by unittests Review URL: https://codereview.chromium.org/1132303005 Cr-Commit-Position: refs/heads/master@{#329567}
-
tommycli authored
Quoting raymes: "What is happening is that while the plugin is initializing it sends a sync IPC which results in re-entrancy. ExecuteScript is being run during re-entrancy which runs a script on the page which can result in layout changing and so reportGeometry can be called." BUG=486674 Review URL: https://codereview.chromium.org/1137433004 Cr-Commit-Position: refs/heads/master@{#329566}
-
brettw authored
This matches the GYP build. Review URL: https://codereview.chromium.org/1134833003 Cr-Commit-Position: refs/heads/master@{#329565}
-
benwells authored
There are more errors coming up after the latest libvpx roll. TBR=oshima@chromium.org BUG=468169 Review URL: https://codereview.chromium.org/1137993006 Cr-Commit-Position: refs/heads/master@{#329564}
-
ananta authored
Blink maintains state for popups whether they are hidden shown etc. So when a popup is shown and an action causes the popup to be hidden then blink changes the state to hidden. If an action causes the popup to be closed on the browser without notifying blink that the popup is going away due to focus being lost on the parent view, then blink assumes that the popup is still visible. As a result clicking again on a select box would just hide the popup as blink thinks the popup is visible. This bug is only triggered in corner cases like ASH where you have one root window parenting everything else. On regular desktop environments clicking outside the browser window while the popup is open would cause activation changes to occur which would ensure that the Blur notification goes through to the browser. The other change is a simple fix in delegate_execute which caused it to crash in debug mode on a multi dll build. Crash occurred because we were looking for version information in base.dll while launching the crash server. BUG=482937 Review URL: https://codereview.chromium.org/1136143005 Cr-Commit-Position: refs/heads/master@{#329563}
-
jlklein authored
BUG=485381 Review URL: https://codereview.chromium.org/1132793005 Cr-Commit-Position: refs/heads/master@{#329562}
-
xiyuan authored
Sync changes could trigger UpdateDriveApps before DriveAppRegistry is populated with data. An empty list from DriveAppRegistry causes all Drive apps be uninstalled. And some Drive apps would cause Gaia cookies to be lost. BUG=449816 TEST=DriveAppProviderTest.UpdateAfterDriveAppRegistryUpdate Review URL: https://codereview.chromium.org/1130903006 Cr-Commit-Position: refs/heads/master@{#329561}
-
michaelpg authored
BUG=485381 Review URL: https://codereview.chromium.org/1135733005 Cr-Commit-Position: refs/heads/master@{#329560}
-
blink-deps-roller authored
Summary of changes available at: https://chromium.googlesource.com/chromium/blink/+log/6394784..76a74c1 TBR=dpranke@chromium.org,alancutter@chromium.org Review URL: https://codereview.chromium.org/1128993006 Cr-Commit-Position: refs/heads/master@{#329559}
-
mtomasz authored
The "configurable" and "multipleMounts" should be optional and default to false. TEST=browser_tests: *FileSystemProvider*Configure*, *FileSystemProvider*Mount* BUG=474146 Review URL: https://codereview.chromium.org/1127283003 Cr-Commit-Position: refs/heads/master@{#329558}
-
servolk authored
When one of the streams is much shorter than other(s), the shorter stream reaches EOS first and then its media time stops increasing, which blocks other streams due to using BalancedMediaTaskRunner. Resetting the media task runner will ensure other streams are not blocked by the shortest one. BUG=internal b/19560149 Review URL: https://codereview.chromium.org/1140003002 Cr-Commit-Position: refs/heads/master@{#329557}
-
hendrikw authored
This moves more of the transitive state of the tile to PrioritizedTile which has a shorter lifetime, avoiding us to update properties on the tile. BUG= Review URL: https://codereview.chromium.org/1132443003 Cr-Commit-Position: refs/heads/master@{#329556}
-
jlklein authored
BUG= Review URL: https://codereview.chromium.org/1141673002 Cr-Commit-Position: refs/heads/master@{#329555}
-
jlklein authored
BUG=485381 Review URL: https://codereview.chromium.org/1135013005 Cr-Commit-Position: refs/heads/master@{#329554}
-
isherman authored
BUG=483276 TEST=none R=tengs@chromium.org Review URL: https://codereview.chromium.org/1113043004 Cr-Commit-Position: refs/heads/master@{#329553}
-
michaelpg authored
BUG=485381 Review URL: https://codereview.chromium.org/1136273002 Cr-Commit-Position: refs/heads/master@{#329552}
-
nparker authored
SafeBrowsingDatabaseManager: Pure interface TestSafeBrowsingDatabaseManager: Dummy impl for tests LocalSafeBrowsingDatabaseManager: Existing full impl. RemoteSafeBrowsingDatabaseManager: New for Android Wire up the safe_browsing=3 build-mode to switch Android to use Remote*. Move SafeBrowsingCheck into Local* and create the Test* impl that can't accidentally call a real implementation's methods. Adjust tests to use either Test* or Local*. The initial implementation of Remote* does the bookeeping of requests, but doesn't yet make calls to Java and isn't tested. BUG=474608 Review URL: https://codereview.chromium.org/1110723002 Cr-Commit-Position: refs/heads/master@{#329551}
-
miu authored
This change allows the client to specify a target sampling rate, aside from the maximum frame rate. When animated content is detected, an approprate subsampling of the relevant frames will be proposed. This is meant to be used for clients wishing to detect high-frame-rate content (e.g., 48 or 60 FPS), but only sample at traditional rates (e.g., 24 or 30 FPS). In testing this change, it became apparent that the current tests were highly sensitive to phase issues, and were erroneously generating discontinuous sequences of events in some scenarios. The tests have been fixed and additional testing for the new functionality added. BUG=156767 Review URL: https://codereview.chromium.org/1123623005 Cr-Commit-Position: refs/heads/master@{#329550}
-
thakis authored
This way, the 64-bit bots will help us find regressions since they build with warnings-as-errors. BUG=467287 Review URL: https://codereview.chromium.org/1139493003 Cr-Commit-Position: refs/heads/master@{#329549}
-
isherman authored
This is a tiny feature rename, per request from the marketing team. BUG=484541 TEST=none R=tengs@chromium.org Review URL: https://codereview.chromium.org/1134163004 Cr-Commit-Position: refs/heads/master@{#329548}
-
Newton Allen authored
Files in chrome/android/sync_shell/javatests use the org.chromium.chrome.browser.sync Java package, but were located under src/chromium/chrome/browser/sync. This fixes the problem by adding an "org" directory. R=nyquist@chromium.org, pvalenzuela@chromium.org TBR=manisicalco@chromium.org Review URL: https://codereview.chromium.org/1132173003 Cr-Commit-Position: refs/heads/master@{#329547}
-
ben authored
R=sky@chromium.org BUG= Review URL: https://codereview.chromium.org/1133893003 Cr-Commit-Position: refs/heads/master@{#329546}
-
dbeam authored
Renamed a class in the HTML and forgot to update CSS. R=estade@chromium.org BUG=487234 Review URL: https://codereview.chromium.org/1133013004 Cr-Commit-Position: refs/heads/master@{#329545}
-
nyquist authored
Currently the SourcePageHandleWebContents holds a scoped_ptr<WebContents>, which means that when distillation of the source page is finished, the WebContents will be destroyed. This makes it hard to distill the contents from one WebContents, and view the result in another. This CL makes the SourcePageHandleWebContents only optionally own the WebContents by taking in a raw pointer an a bool flag of whether it should own it or not. In the current chrome-level API DistillCurrentPageAndView the old behavior is kept, and the source WebContents is destroyed when distillation finishes. In addition, this CL adds a new chrome-level API DistillAndView(...), where the caller passes in two WebContents, one for the source page, and one for where the caller wants to view the distilled content. The distiller code does in this case not take ownership of any of these. BUG=None TEST=browser_tests,components_browsertests Review URL: https://codereview.chromium.org/1058193002 Cr-Commit-Position: refs/heads/master@{#329544}
-
nasko authored
BUG=486889 Review URL: https://codereview.chromium.org/1141453003 Cr-Commit-Position: refs/heads/master@{#329543}
-
donnd authored
Adds handling to show the selection handles for a tap or long-press on an existing selection that does not yet show the selection handles. This approach works fine when the selection does not wrap, and it's currently very rare that we have a multi-line selection. However, some day we'll have the ability to expand the selection, so we should revisit this implementation then. More info on this in issue 393025. Based on CL 1086393003 by jdduke@. BUG=chromium:393025, chromium:420281 Review URL: https://codereview.chromium.org/1102933003 Cr-Commit-Position: refs/heads/master@{#329542}
-
jochen authored
When we close a tab that shows a modal dialog, and another tab has a modal dialog pending, we'll end up deactivating the first tab after closing it. In that case, just ignore the event. BUG=484550 R=kalman@chromium.org Review URL: https://codereview.chromium.org/1141493002 Cr-Commit-Position: refs/heads/master@{#329541}
-
blink-deps-roller authored
Summary of changes available at: https://chromium.googlesource.com/chromium/blink/+log/f0a5894..6394784 TBR=dpranke@chromium.org,alancutter@chromium.org Review URL: https://codereview.chromium.org/1138813004 Cr-Commit-Position: refs/heads/master@{#329540}
-