- 30 Aug, 2016 40 commits
-
-
peconn authored
By rendering the root view we include the Toolbar in the new_tab_page renders. BUG=641975 Review-Url: https://codereview.chromium.org/2288363002 Cr-Commit-Position: refs/heads/master@{#415144}
-
rdevlin.cronin authored
SyncExtensionFunctions, AsyncExtensionFunctions, ChromeSyncExtensionFunctions, and ChromeAsyncExtensionFunctions are deprecated. Remove SyncExtensionFunctions from: - idltest - test - system_display BUG=634140 Review-Url: https://codereview.chromium.org/2282063002 Cr-Commit-Position: refs/heads/master@{#415143}
-
thestig authored
TBR=dbeam@chromium.org Review-Url: https://codereview.chromium.org/2289543004 Cr-Commit-Position: refs/heads/master@{#415142}
-
bashi authored
When memory coordinator is enabled, HistoryBackend becomes a client of memory coordinator instead of installing MemoryPressureListener. Also MemoryCoordinator becomes a singleton so that any component can access MemoryCoordinator to listen to memory events. BUG=639700 Review-Url: https://codereview.chromium.org/2261073002 Cr-Commit-Position: refs/heads/master@{#415141}
-
bartfab authored
We distinguish three cases: * Policies that control browser behavior. These implicitly apply to Chrome on Chrome OS only. No documentation updates are needed. * Policies that affect parts of the system which lie outside the scope of ARC, e.g. the login screen and auto-update system. These implicitly apply to Chrome OS only. No documentation updates are needed. * Policies that directly or indirectly influence app behavior. The default assumption is that any such policy applies to both Chrome and Android apps. This CL adds a note to the generated documentation whenever this is not the case. BUG=b/28039197 b/28109303 TEST=ninja -C out/out policy_templates Review-Url: https://codereview.chromium.org/2278493004 Cr-Commit-Position: refs/heads/master@{#415140}
-
yukishiino authored
It's more convenient for call sites to let ExceptionState throw by default than to explicitly call to throwIfNeeded(). This prevents a mistake that a call site forgets to throw. ExceptionState now looks a kind of exception scope. BUG= Review-Url: https://codereview.chromium.org/2272613003 Cr-Commit-Position: refs/heads/master@{#415139}
-
alph authored
These can come out of user timings on timeline. Review-Url: https://codereview.chromium.org/2288853002 Cr-Commit-Position: refs/heads/master@{#415138}
-
dgozman authored
- Do not list inspector_protocol files anywhere outside; - Separate concatenation from compatibility check; - Improve files layout; - Pass path to jinja module to CodeGenerator. BUG=637032 Review-Url: https://codereview.chromium.org/2282283002 Cr-Commit-Position: refs/heads/master@{#415137}
-
khmel authored
In some cases, Arc window may be destroyed and created again. This leads to situation when shelf item is closed and there is no longer item for Arc task. This CL allows Arc window to be recreated. The situation may go even worse, window may be destroyed and not created after. In this case we have task without window. In this case, we send launch request to Android and this put Android task to foreground and window is created. BUG=b/31071902 TEST=Manually on device, installed several photo editor apps as described in task. Minimize/maximize window. Sometimes window get destroyed and created again. Shelf item is not lost in this case. Sometimes window destroyed and not recreated. Shelf icon still exists and clicking on it gets new window back for task. TEST=Extended unit_tests Review-Url: https://codereview.chromium.org/2282023002 Cr-Commit-Position: refs/heads/master@{#415136}
-
wfh authored
BUG=455496 Review-Url: https://codereview.chromium.org/2294463002 Cr-Commit-Position: refs/heads/master@{#415135}
-
rtoy authored
Internally clamp loopStart to lie within the bounds of the buffer. Also add some assertions that the read and write indices for the input and output buffers lie within the expected bounds. BUG=641234 TEST= Review-Url: https://codereview.chromium.org/2282103002 Cr-Commit-Position: refs/heads/master@{#415134}
-
eyaich authored
waterfall. chromium.perf.json: This file should not change in overall content although some of the ordering may be off. I have also explicitly set the shards for Win 7 Intel GPU Perf given the format my script expects, which is the same as the current json file which doesn't specify a shard. Note: I have removed entries for bots that are not longer on our waterfall. These include Win 7 Low-End Perf, Mac 10.9 and Mac 10.8. This is simply cleanup and doesn't impact any functionality. chromium.perf.fyi.json: This file is new and doesn't have any configuration yet that will actually read this file. The next step is to trigger the jobs locally before I change the fyi recipes to read from this json file. Note: telemetry_perf_tests will be the name of the gn target in a follow up cl. Note that this file will probably change as I iterate on getting the perf tests swarmed. BUG=chromium:633253 Review-Url: https://codereview.chromium.org/2272603005 Cr-Commit-Position: refs/heads/master@{#415133}
-
pdfium-deps-roller authored
https://pdfium.googlesource.com/pdfium.git/+log/548ea2f7d083..35512aa7e4ac $ git log 548ea2f7d..35512aa7e --date=short --no-merges --format='%ad %ae %s' 2016-08-29 jaepark Display content of the annotation when mouse hover. 2016-08-29 dsinclair Skip the channel if there is no data. 2016-08-29 tsepez Revert "Add -> operators to CFX_CountRef." 2016-08-29 tsepez Revert "Replace wrapper methods in CPDF_Path with -> operator." 2016-08-29 tsepez Revert "Use ->() in CPDF_ColorState" 2016-08-29 tracy_jiang Fix for #618267. Adding a method to determine if multiplication has overflow. 2016-08-29 dsinclair Verify element exists before accessing. 2016-08-29 tsepez Use ->() in CPDF_ColorState 2016-08-29 stackexploit openjpeg: Prevent an integer overflow in opj_jp2_apply_pclr. 2016-08-29 dsinclair Initialize the CPDF_Document pointer 2016-08-29 tsepez Replace wrapper methods in CPDF_Path with -> operator. 2016-08-29 thestig Add some limit checks to ReadSharedObjHintTable(). 2016-08-29 npm Move CFX_SubstFont and CTTFontDesc into their own files 2016-08-29 tonikitoo Fix the test case added in https://codereview.chromium.org/2277063003/ BUG=62625,637232,618267,641076,638829,640998,641444 TBR=dsinclair@chromium.org Review-Url: https://codereview.chromium.org/2293733002 Cr-Commit-Position: refs/heads/master@{#415132}
-
aizatsky authored
BUG= Review-Url: https://codereview.chromium.org/2288403002 Cr-Commit-Position: refs/heads/master@{#415131}
-
azurewei authored
BUG=642218 TEST=Verified on local build. Review-Url: https://codereview.chromium.org/2282403004 Cr-Commit-Position: refs/heads/master@{#415130}
-
glevin authored
BUG=612181 TEST=Should be no difference in battery percent display in SysTray menu Small cleanup from prior i18n work Review-Url: https://codereview.chromium.org/2286353002 Cr-Commit-Position: refs/heads/master@{#415129}
-
trizzofo authored
Removes PluginCache and reload PluginData's plugin list whenever the origin changes. Use origin url to retrieve new plugin list. This is needed because, after HTML5 by Default is implemented, the plugin list will depend on the current web page url (settings url exceptions). Here is more information about HTML5 by Default: go/hbd-design-doc BUG=626728 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation Review-Url: https://codereview.chromium.org/2156803002 Cr-Commit-Position: refs/heads/master@{#415128}
-
yosin authored
This patch converts "editing/inserting/multiple-lines-selected.html" to use w3c test harness to simplify test script for improving readability. BUG=n/a TEST=n/a; no behavior changes Review-Url: https://codereview.chromium.org/2286263002 Cr-Commit-Position: refs/heads/master@{#415127}
-
v8-autoroll authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/54b0bb84..a9f1ddb6 Please follow these instructions for assigning/CC'ing issues: https://github.com/v8/v8/wiki/Triaging%20issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel TBR=hablich@chromium.org,machenbach@chromium.org,littledan@chromium.org,vogelheim@chromium.org Review-Url: https://codereview.chromium.org/2291563002 Cr-Commit-Position: refs/heads/master@{#415126}
-
shrike authored
A recent cl that adjusted bookmark bar layout changed the left and right bookmark item indent to an incorrect value. This cl corrects that mistake. R=avi@chromium.org BUG=640134 Review-Url: https://codereview.chromium.org/2293593002 Cr-Commit-Position: refs/heads/master@{#415125}
-
danakj authored
When the UIResource is larger than max_texture_size, we downsample it into a smaller bitmap. However floating point precision can cause some of the pixels to not be fully initialized if the scale doesn't exactly cause the bitmap to be filled. So clear the bitmap before doing this scaling operation into it. R=enne BUG=642011 CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel Review-Url: https://codereview.chromium.org/2292713002 Cr-Commit-Position: refs/heads/master@{#415124}
-
bugsnash authored
This is the first step in making PassRefPtr move only, in preparation for removal of PassRefPtr. BUG=640449 Review-Url: https://codereview.chromium.org/2274793002 Cr-Commit-Position: refs/heads/master@{#415123}
-
fgorski authored
BUG=641858 R=dimich@chromium.org Review-Url: https://codereview.chromium.org/2285163003 Cr-Commit-Position: refs/heads/master@{#415122}
-
gcomanici authored
Chrome will defer to an existing browser via the process singleton during startup. When the existing browser appears hung, Chrome will prompt the user to kill it. If the user consents, Chrome will now try to acquire the singleton and continue with startup rather than exit. BUG=603698 TEST=see bug Review-Url: https://codereview.chromium.org/2271833002 Cr-Commit-Position: refs/heads/master@{#415121}
-
eroman authored
* Errors are identified by strings * Errors may contain parameters * Chain verification may set multiple errors/warnings This is an initial stab at the problem, and there are multiple TODOs to follow-up on. BUG=634443 Review-Url: https://codereview.chromium.org/2282183004 Cr-Commit-Position: refs/heads/master@{#415120}
-
lanwei authored
In ConvertLocationToTarget function, the offset added to the event location is not scaled, so we should apply the screen scale factor to the event location after it has been transformed to the target. Then we can find the right target to send the event using the correct coordinates. BUG=634343 Review-Url: https://codereview.chromium.org/2269483002 Cr-Commit-Position: refs/heads/master@{#415119}
-
chenwilliam authored
BUG=627296 Review-Url: https://codereview.chromium.org/2286413003 Cr-Commit-Position: refs/heads/master@{#415118}
-
dschuyler authored
This CL puts the font size and example text in the same span so that they get properly aligned and wrapped. The effect (the bug or fix) is noticeable with huge font sizes (48 pt and higher). BUG=613203 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Review-Url: https://codereview.chromium.org/2284133002 Cr-Commit-Position: refs/heads/master@{#415117}
-
yoichio authored
1. Both |draggable| and |-webkit-user-drag| mean the element with the attributes is dragged when user drags pointer: 2. |draggeble| is the HTML5 standard but |-webkit-user-drag| is not: https://w3c.github.io/html/editing.html#drag-and-drop 3. Thus we should deprecate |-webkit-user-drag| for interoperability. However, |-webkit-user-drag| is used 4% in wild. That's high to deprecate immediately: https://www.chromestatus.com/metrics/css/timeline/popularity/337 But if |draggable| is used higher than |-webkit-user-drag|, we can accelarate that stream by deprecating |-webkit-user-drag|. Review-Url: https://codereview.chromium.org/2234733002 Cr-Commit-Position: refs/heads/master@{#415116}
-
rmistry authored
BUG=chromium:641003 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq Review-Url: https://codereview.chromium.org/2278653004 Cr-Commit-Position: refs/heads/master@{#415115}
-
kkhorimoto authored
The WKWebViewConfiguration's |userScripts| are not injected when navigating via BFLI to a page created using window.history.pushState. This means that calling window.history navigation functions will invoke WKWebView's non-overridden implementations, causing a mismatch between the WKBackForwardList and NavigationManager. BUG=none Review-Url: https://codereview.chromium.org/2292773002 Cr-Commit-Position: refs/heads/master@{#415114}
-
estevenson authored
Importing //tools into gcc_toolchain.gni breaks certain downstream projects that include //build but not //tools. This CL changes gcc_toolchain.gni to only rely on files within //build. BUG=641981 Review-Url: https://codereview.chromium.org/2288273002 Cr-Commit-Position: refs/heads/master@{#415113}
-
yusufo authored
This starts sending bounds information from exteral prerenders and uses that to store a default_bounds_ rectangle in RWHV Android rather than a size. This basically updates the default size to also take into account the top controls offset needed in the physical backing size. With this we can get the page composited properly during prerendering. Note that this doesn't resolve the bug yet, since we still need an abstraction layer (possibly a NativeView) that will hold this default_bounds_ information. BUG=628302 Review-Url: https://codereview.chromium.org/2268323003 Cr-Commit-Position: refs/heads/master@{#415112}
-
thestig authored
Review-Url: https://codereview.chromium.org/2290453004 Cr-Commit-Position: refs/heads/master@{#415111}
-
sorin authored
The code in DefaultComponentInstaller::FinishRegistration is not updating the value of CrxComponent::supports_group_policy_enable_component_updates with the value provided by the specific installer traits. Therefore, the components using the DefaultComponentInstaller for their installer ignore the group policy settings for controlling the update behavior. BUG=642148 Review-Url: https://codereview.chromium.org/2292463004 Cr-Commit-Position: refs/heads/master@{#415110}
-
yyanagisawa authored
Since we are going to make whitelisted targets to zero, there is no reason to avoid to check details on expected diffs. BUG=314403 Review-Url: https://codereview.chromium.org/2289643002 Cr-Commit-Position: refs/heads/master@{#415109}
-
avi authored
BUG=555865 Review-Url: https://codereview.chromium.org/2284863002 Cr-Commit-Position: refs/heads/master@{#415108}
-
joedow authored
This change adds a Chrome enterprise policy to control whether or not we use the uiAccess enabled binary for It2Me or the binary which runs at the user's integrity level. BUG=617185 Review-Url: https://codereview.chromium.org/2252243002 Cr-Commit-Position: refs/heads/master@{#415107}
-
oka authored
BUG=641617 TEST=manually tested. Review-Url: https://codereview.chromium.org/2288663002 Cr-Commit-Position: refs/heads/master@{#415106}
-
pfeldman authored
BUG=640375 Review-Url: https://codereview.chromium.org/2287713002 Cr-Commit-Position: refs/heads/master@{#415105}
-