summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Publish DEPS for Chromium 44.0.2403.7044.0.2403.70chrome-tpm2015-06-291-644/+542
|
* Incrementing VERSION to 44.0.2403.70chrome-tpm2015-06-301-1/+1
| | | | | Cr-Commit-Position: refs/branch-heads/2403@{#424} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Hide "Add user" button when enrollment screen is active.Pavel Sergeev2015-06-293-0/+9
| | | | | | | | | | | | | | | BUG=504014 TEST=manually Review URL: https://codereview.chromium.org/1207893004 Cr-Commit-Position: refs/heads/master@{#336314} (cherry picked from commit 221df22843b58e74a2ccfb639d26c7aa4644bfa9) Review URL: https://codereview.chromium.org/1217753004. Cr-Commit-Position: refs/branch-heads/2403@{#423} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Merge to M44 adding of Chromoting extension IDs to approved list of ↵anandc2015-06-291-1/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | metricsPrivate API. Add extension IDs for all versions of remoting apps to permissions list of metricsPrivate API. BUG=500086 TBR=jamiewalch NOTRY=true NOPRESUBMIT=true Review URL: https://codereview.chromium.org/1184353005 Cr-Commit-Position: refs/heads/master@{#334687} (cherry picked from commit e46057f84c4333c480b5cc28e39bac57abd8b673) Add Chrome Remote Desktop to approved extensions list of metrics-private API. BUG=500086 Review URL: https://codereview.chromium.org/1186983002 Cr-Commit-Position: refs/heads/master@{#334486} (cherry picked from commit c1dfbaf1805e30dbb31b2f18cb008ceba51ed460) Review URL: https://codereview.chromium.org/1215733003 Cr-Commit-Position: refs/branch-heads/2403@{#422} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Remove custom material styling for EditText in preferencesTheresa Wellington2015-06-292-20/+0
| | | | | | | | | | | | | | | | | This is implemented in AppCompat now and our custom implementation was causing bugs (e.g. the cursor was showing up white). BUG=497608 TBR=aurimas@chromium.org Review URL: https://codereview.chromium.org/1169903003 Cr-Commit-Position: refs/heads/master@{#333762} Review URL: https://codereview.chromium.org/1210153005. Cr-Commit-Position: refs/branch-heads/2403@{#421} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* win10: Fix various ui glitchesScott Graham2015-06-292-39/+60
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This addresses the most egregious problems so that we look more or less like a reasonable app on Win10. In particular, fixes a too-wide border, removing the rounded corners on the toolbar that don't work when there's no border (see 504044 for agreement from UX), and an ugly overhang in the non-client area in the top-left and top-right of the window. In case you're not familiar with Win10 UI style (I wasn't!) I put a composite of what standard apps plus before/after this patch here http://i.imgur.com/JxNJvBv.png . We aren't easily able to switch to a more "grey"-style title bar at the moment as that's reserved for Windows-store applications (plain Win32 apps like notepad and chrome always get the white title bar style). We might want to look into that in the future as it's pretty harsh, but at least we match the expected system behaviour this way. R=pkasting@chromium.org BUG=504044,502001 Review URL: https://codereview.chromium.org/1209723004 Cr-Commit-Position: refs/heads/master@{#336438} (cherry picked from commit 48ddea097cd6bd2ef0fc4d133834b55d3b6d99fc) Review URL: https://codereview.chromium.org/1213243002. Cr-Commit-Position: refs/branch-heads/2403@{#420} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Rebuild PropertyTrees When Layer Attach to New LayerTreeHostWeiliang Chen2015-06-292-0/+16
| | | | | | | | | | | | | | | | | | | | | | | | | When detach a layer from old LayerTreeHost and attach it to new one, both old and new LayerTreeHost need to rebuild their property trees. Layer now has stale indices for property trees, invalidate them. Old LayerTreeHost also needs to be rebuilt because detaching a layer might change the property trees' structures. This change needs to go into M44. BUG=497952,504959 TBR=enne, vollick CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel Review URL: https://codereview.chromium.org/1166233002 Cr-Commit-Position: refs/heads/master@{#333417} (cherry picked from commit c4d2e74d6d68fd7ed55ec11df3151ec4208dfffa) Review URL: https://codereview.chromium.org/1217883002. Cr-Commit-Position: refs/branch-heads/2403@{#419} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Disable "Ok Google" hotwording in open source builds by default.Matt Giuca2015-06-293-20/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The compile-time flag "enable_hotwording" is now tied to branding=Chrome (false by default unless making a Google Chrome build). Note: Chromium will no longer download/install the Hotword Shared Module, and will automatically remove the Hotword Shared Module on startup if it was previously installed. To keep this functionality, add "enable_hotwording=1" to GYP_DEFINES. BUG=500922 Review URL: https://codereview.chromium.org/1200413003 Cr-Commit-Position: refs/heads/master@{#335874} (cherry picked from commit 0366a5184a70b3eefb5fcef2c2e13721669f00d8) Fix up HotwordServiceTest on Chrome-branded builds. The ENABLE_HOTWORDING flag is not available in hotword_service_unittest.cc, so all tests were assuming hotwording was disabled (since r333548). This has been failing on Official builders since r335874. Since it's hard to resolve this in a simple way (we want to merge these changes), just disabling the tests is the cleanest option for now. BUG=503963 Review URL: https://codereview.chromium.org/1207163002 Cr-Commit-Position: refs/heads/master@{#336091} (cherry picked from commit 8ef0bc35b1594ad013dc2ae1d6893e0091919271) Resolved merge conflict: Disabled IsHotwordAllowedDisabledFieldTrial and IsHotwordAllowedInvalidFieldTrial. These tests were deleted before the upstream patch landed. (Merge approval on http://crbug.com/500922#c69) R=thakis@chromium.org TBR=thakis@chromium.org Committed: https://chromium.googlesource.com/chromium/src/+/86fb78f02492b2990307ed427c09670f2fff0d3b Review URL: https://codereview.chromium.org/1211273003. Cr-Commit-Position: refs/branch-heads/2403@{#418} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Revert "Disable "Ok Google" hotwording in open source builds by default."Matt Giuca2015-06-293-44/+18
| | | | | | | | | | | | | | This reverts commit 86fb78f02492b2990307ed427c09670f2fff0d3b. Commit broke the build due to merge failure. BUG=505351 TBR=thakis@chromium.org Review URL: https://codereview.chromium.org/1218763002. Cr-Commit-Position: refs/branch-heads/2403@{#417} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Disable "Ok Google" hotwording in open source builds by default.Matt Giuca2015-06-293-18/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The compile-time flag "enable_hotwording" is now tied to branding=Chrome (false by default unless making a Google Chrome build). Note: Chromium will no longer download/install the Hotword Shared Module, and will automatically remove the Hotword Shared Module on startup if it was previously installed. To keep this functionality, add "enable_hotwording=1" to GYP_DEFINES. BUG=500922 Review URL: https://codereview.chromium.org/1200413003 Cr-Commit-Position: refs/heads/master@{#335874} (cherry picked from commit 0366a5184a70b3eefb5fcef2c2e13721669f00d8) Fix up HotwordServiceTest on Chrome-branded builds. The ENABLE_HOTWORDING flag is not available in hotword_service_unittest.cc, so all tests were assuming hotwording was disabled (since r333548). This has been failing on Official builders since r335874. Since it's hard to resolve this in a simple way (we want to merge these changes), just disabling the tests is the cleanest option for now. BUG=503963 Review URL: https://codereview.chromium.org/1207163002 Cr-Commit-Position: refs/heads/master@{#336091} (cherry picked from commit 8ef0bc35b1594ad013dc2ae1d6893e0091919271) Resolved merge conflict: Disabled IsHotwordAllowedDisabledFieldTrial and IsHotwordAllowedInvalidFieldTrial. These tests were deleted before the upstream patch landed. (Merge approval on http://crbug.com/500922#c69) R=thakis@chromium.org TBR=thakis@chromium.org Review URL: https://codereview.chromium.org/1211273003. Cr-Commit-Position: refs/branch-heads/2403@{#416} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* chrome://voicesearch: Change some labels to clarify their meaning.Matt Giuca2015-06-291-3/+8
| | | | | | | | | | | | | | | | | | | | | | Also added a new field, "Hotword Module Installable", which shows whether Chrome can install the hotword module at all. This will be false if hotwording is disabled at compile time, or if the user's language is not supported. BUG=503496 Review URL: https://codereview.chromium.org/1196243003 Cr-Commit-Position: refs/heads/master@{#335871} (cherry picked from commit 142111475c337af89b7645eed66194cd36d93120) (Merge approval on http://crbug.com/500922#c69) TBR=pkasting@chromium.org Review URL: https://codereview.chromium.org/1213093002. Cr-Commit-Position: refs/branch-heads/2403@{#415} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* (M44) ServiceWorker: Fix matching registration info missing during shift-reload.Matt Falkenhagen2015-06-294-0/+26
| | | | | | | | | | | | | | | | | | | | | | | | | Currently the new document generated by shift-reload doesn't retain any previous matching registration info, then the .ready or .claim() can't find correct registration through MatchRegistration(). This CL will add all living matching registrations to the new provider host. The old provider host will keep related registrations alive until provisional load be committed. Layout test CL: https://codereview.chromium.org/1184923005/ BUG=462529 Review URL: https://codereview.chromium.org/1181573010 Cr-Commit-Position: refs/heads/master@{#336127} (cherry picked from commit 4310022a0cb532805f13ba2ca0d6d048795e1949) TBR=xiang.long@intel.com Review URL: https://codereview.chromium.org/1219623002. Cr-Commit-Position: refs/branch-heads/2403@{#414} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* [Merge] ServiceWorker: Directly delete database directory instead of ↵Hiroki Nakagawa2015-06-296-101/+206
| | | | | | | | | | | | | | | | | | | | | | | | | leveldb::DestroyDB When a database directory contains files not related to LevelDB, DestroyDB() does not delete the directory and leaves those files. This non-empty database directory infinitely fails ServiceWorkerDatabase::LazyOpen during a session. (See my comment #24 in the issue for more details). To avoid that, this CL directly deletes the directory instead of DestroyDB. BUG=468926 TEST=content_unittests --gtest_filter=ServiceWorkerResourceStorageDiskTest.DeleteAndStartOver* TBR=falken@chromium.org Review URL: https://codereview.chromium.org/1176203007 Cr-Commit-Position: refs/heads/master@{#335893} (cherry picked from commit 0bd5fd70714ca1ae846be5b657fd3a21f49884c1) Review URL: https://codereview.chromium.org/1214793006. Cr-Commit-Position: refs/branch-heads/2403@{#413} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Add build flag to disable hotwording.Matt Giuca2015-06-295-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | Hotwording downloads a shared module from the web store containing a NaCl module. There is a desire to build and distribute Chromium without this happening. This change adds an "enable_hotwording" build flag that is enabled by default, but can be disabled at compile time. BUG=491435 Review URL: https://codereview.chromium.org/1160243004 Cr-Commit-Position: refs/heads/master@{#333548} (cherry picked from commit f269d3b548203e217e8c0080c2e22e7ae3efb51e) Resolved merge conflict: Remove the body of IsHotwordAllowedDisabledFieldTrial and IsHotwordAllowedInvalidFieldTrial when ENABLE_HOTWORDING is false. These tests were deleted before the upstream patch landed. (Merge approval on http://crbug.com/500922#c69) TBR=thestig@chromium.org,scottmg@chromium.org Review URL: https://codereview.chromium.org/1218693004. Cr-Commit-Position: refs/branch-heads/2403@{#412} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Incrementing VERSION to 44.0.2403.69chrome-tpm2015-06-271-1/+1
| | | | | Cr-Commit-Position: refs/branch-heads/2403@{#411} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* [Merge] Fix a crash due to destruction order in ProfileManager.Roger Tawa2015-06-261-5/+7
| | | | | | | | | | | | | | | | | | | | The ProfileInfo destructor can initiate a call chain that uses ProfileManager::profile_info_cache_ indirectly, which was causing a crash since the latter was destroyed before the ProfileManager::profiles_info_ destructor. BUG=501306 TBR=anthonyvd@chromium.org Review URL: https://codereview.chromium.org/1197733005 Cr-Commit-Position: refs/heads/master@{#335946} (cherry picked from commit 2b6846010ed1f524ecd55099c3663c27a33c7158) Review URL: https://codereview.chromium.org/1213453003. Cr-Commit-Position: refs/branch-heads/2403@{#410} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Incrementing VERSION to 44.0.2403.68chrome-tpm2015-06-261-1/+1
| | | | | Cr-Commit-Position: refs/branch-heads/2403@{#409} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* branch 2403 fork: Drop gpu raster resources in android webviewBo Liu2015-06-261-0/+14
| | | | | | | | | | | | | | | | This is a more contained fork of the fix in https://codereview.chromium.org/1146313004 Drop gpu raster resources when webview memory is supposed to be released. BUG=502331 TBR=boliu@chromium.org Review URL: https://codereview.chromium.org/1200863003. Cr-Commit-Position: refs/branch-heads/2403@{#408} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Revert "cc: Make tiling interest rect calc based on viewport."Jared Duke2015-06-2622-49/+99
| | | | | | | | | | | | | | | | | This reverts commit 6d84db54a27c036d77b0e4a26d42c158ee4a6add. Reason for revert: This creates perf regression with top-controls and viewport resizes on Android (creates and deletes extra tiles). TBR=vmpstr@chromium.org BUG=502432 Review URL: https://codereview.chromium.org/1217513002. Cr-Commit-Position: refs/branch-heads/2403@{#407} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Fix crash in drive::BatchRequestConfigurator::MultipartUploadNewFile.Daichi Hirono2015-06-267-23/+124
| | | | | | | | | | | | | | | | | | | | | | | | | | Previously the configuretor held the batch request to configure, and it assumed the batch request has not been released before it is committed. But the batch request was passed to request sender when it is created, and actually the request sender could release the batch request before sending it when pre-authentication was failure. Thus it crashed when adding new child request to the released batch request. The CL adds check for the batch request, and passes DRIVE_OTHER_ERROR for child requests in the case that the parent batch request has already been released. BUG=503433 TEST=DriveAPIServiceTest.BatchRequestConfiguratorWithAuthFailure TBR=mtomasz@chromium.org,kinaba@chromium.org Review URL: https://codereview.chromium.org/1198273009 Cr-Commit-Position: refs/heads/master@{#336098} (cherry picked from commit 98b515b0378d5b88de9f6901f8bc726a94ce6ec4) Review URL: https://codereview.chromium.org/1209253003. Cr-Commit-Position: refs/branch-heads/2403@{#406} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Merge to M44: Gallery: do not capture keys when share dialog is open.Yuki Awano2015-06-261-0/+5
| | | | | | | | | | | | | | | | BUG=502410 TEST=manually tested; Open share dialog in gallery and type keys. The gallery should not respond to keys (previously it toggled to edit mode when a user pressed E key in share dialog). TBR=hirono@chromium.org Review URL: https://codereview.chromium.org/1198943005 Cr-Commit-Position: refs/heads/master@{#335632} (cherry picked from commit 6190b03157f9f4ac82dd3c0d5453e7604f90ff45) Review URL: https://codereview.chromium.org/1209353002. Cr-Commit-Position: refs/branch-heads/2403@{#405} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Finish composing text when a new input connection is madeChangwan Ryu2015-06-263-2/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we lock the screen, View#onCreateInputConnection() is called and a new input connection is made. At the initialization, we remove the composing spans to avoid keyboard status conflict. However, since we do not tell the Blink editor about the removal, the Blink editor thinks that we are still composing something. IME calls finishComposingText() on the input connection, but we never update the composing region because of the empty composing span check in finishComposingText(). Now the sync between Blink editor and browser editor is completely broken, so some badness may follow after the user unlocks the screen. It is not desirable to remove composing spans arbitrarily. We can replace this by finishComposingText(). BUG=503501 Review URL: https://codereview.chromium.org/1196183005 Cr-Commit-Position: refs/heads/master@{#336309} (cherry picked from commit 8402ae722c480237949e2e219a4bcfbe0146b77c) Review URL: https://codereview.chromium.org/1212183003. Cr-Commit-Position: refs/branch-heads/2403@{#404} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Incrementing VERSION to 44.0.2403.67chrome-tpm2015-06-261-1/+1
| | | | | Cr-Commit-Position: refs/branch-heads/2403@{#403} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Incrementing VERSION to 44.0.2403.66chrome-tpm2015-06-251-1/+1
| | | | | Cr-Commit-Position: refs/branch-heads/2403@{#402} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* To M44: MSE: Prevent a Remove() following a satisfied Seek() from causing stallMatt Wolenetz2015-06-253-16/+189
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change prevents playback stall (without requiring web apps to use a seek workaround) when buffered media is removed at the current position (and later appended again), when there has been no satisfied read from the SourceBufferStream at this position since the last Seek was satisfied. Updated and new unit tests are included, and minimized repro at http://bl.ocks.org/wolenetz/0f726aed2b36af0a261e appears fixed by this change. BUG=478151 TEST=SourceBufferStreamTest.{SeekToStart*,*ReSeek*,Remove_WholeGOPBeingAppended}, no local media layout test regression Review URL: https://codereview.chromium.org/1189663002 Cr-Commit-Position: refs/heads/master@{#335853} (cherry picked from commit 6f2063ea9711e80b6676d7372c83657d13f8205f) In this merge to M44, I manually resolved conflicts in media/filters/source_buffer_stream_unittests.cc due to minor test refactor https://crrev.com/24dc553375ee8f668644a04b11c0ed4e188495bc is not in M44. TBR=chcunningham@chromium.org,dalecurtis@chromium.org Review URL: https://codereview.chromium.org/1210913003. Cr-Commit-Position: refs/branch-heads/2403@{#401} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Merge r334996 to M44 branch 2403Noel Gordon2015-06-252-3/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | https://crrev.com/9c5cf06617232b00842383ff001c49fe058fc6b4 r334996 lut_inverse_interp16: interpolate degenerate zeros in TRC curves Degenerate TRC have runs of 0's / 1's from the left / right edge of the TRC curve (a curve we want to invert, to be able to use a color profile as a monitor profile). The inverse TRC of degenerate curves is not well-defined in the run of 0's area (infinite slope). Some monitor calibration software in the field produce 0 runs, thus degenerate TRC, and QCMS setting the inverse of the run to 0's area to 0 causes a color cast (burn) effect on web images corrected with the associated color profile: issue 492379 . Fix that by interpolating the (imaginary) inverse in the 0 run area instead of clamping the inverse to 0. Add more assert conditions to the curve inversion algorithm and also check for an inverted binary search range (these two changes from the related Mozilla bug). TBR=kbr@chromium.org BUG=458024,492379 Review URL: https://codereview.chromium.org/1209863003. Cr-Commit-Position: refs/branch-heads/2403@{#400} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* PDF: Make viewing PDFs when inside a webview work again.Sam McNally2015-06-251-1/+3
| | | | | | | | | | | | | | | | | | This was broken in https://crrev.com/33f9fc827ddb8db53e357bcd50cf20fb4c6a0711. Review URL: https://codereview.chromium.org/1189293002 Cr-Commit-Position: refs/heads/master@{#335467} (cherry picked from commit 00a972c0a0797474b5424c5b773fd04442df2087) BUG=500027 TBR=raymes@chromium.org Review URL: https://codereview.chromium.org/1209853002. Cr-Commit-Position: refs/branch-heads/2403@{#399} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* PDF: Pass the tab ID to chrome.tabs.getZoomSettings.Sam McNally2015-06-251-27/+34
| | | | | | | | | | | | | | | | BUG=500027 Review URL: https://codereview.chromium.org/1189813003 Cr-Commit-Position: refs/heads/master@{#334987} (cherry picked from commit 33f9fc827ddb8db53e357bcd50cf20fb4c6a0711) TBR=raymes@chromium.org Review URL: https://codereview.chromium.org/1211733002. Cr-Commit-Position: refs/branch-heads/2403@{#398} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* QUIC - Fix QUIC enabled experiment spending significantly more timeRaman Tenneti2015-06-2513-325/+231
| | | | | | | | | | | | | | | | | | | | | | | | verifying certs on Android. Get computed CertVerifier::VerifyFlags from SSLConfig from HttpStreamFactoryImpl::Job and pass them to QUIC's CertVerifier code. With this change, when SSLClientSocket[NSS|OpenSSL] code tries to verify the code, certs are already cached and we don't verify certs twice. BUG=502509 R=rch@chromium.org Review URL: https://codereview.chromium.org/1197823002 Cr-Commit-Position: refs/heads/master@{#335463} (cherry picked from commit a75df625713c20eff6faf082248aad9f34cf6a6f) Review URL: https://codereview.chromium.org/1208723002. Cr-Commit-Position: refs/branch-heads/2403@{#397} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Incrementing VERSION to 44.0.2403.65chrome-tpm2015-06-251-1/+1
| | | | | Cr-Commit-Position: refs/branch-heads/2403@{#396} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* [Extensions] Fix ScriptInjection crashDevlin Cronin2015-06-246-10/+112
| | | | | | | | | | | | | If an extension's script injects into all frames and removes a child frame, it should not then try to inject into that child frame. BUG=500574 R=dcheng@chromium.org Review URL: https://codereview.chromium.org/1202733004. Cr-Commit-Position: refs/branch-heads/2403@{#395} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Allow Google Update to impersonate the client for on-demand update checks.Greg Thompson2015-06-241-28/+62
| | | | | | | | | | | | | | | | | | | This is a speculative fix for ERROR_BAD_IMPERSONATION_LEVEL (0x80070542) errors for system-level on-demand update checks. BUG=496313 R=ganesh@chromium.org, pkasting@chromium.org Review URL: https://codereview.chromium.org/1160273006 Cr-Commit-Position: refs/heads/master@{#334055} (cherry picked from commit f2546da00c199e0bd1205fad88c2c7b61d64430c) TBR=grt@chromium.org Review URL: https://codereview.chromium.org/1211643002. Cr-Commit-Position: refs/branch-heads/2403@{#394} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Incrementing VERSION to 44.0.2403.64chrome-tpm2015-06-241-1/+1
| | | | | Cr-Commit-Position: refs/branch-heads/2403@{#393} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Revert "branch 2403 fork: Drop gpu raster resources in android webview"Alex Mineer2015-06-241-14/+0
| | | | | | | | | | | This reverts commit a08040a32fa6cb9eea493c3747d1a2d48eb9b502. Reverting for the time being due to a graphics regression BUG=502331 Cr-Commit-Position: refs/branch-heads/2403@{#392} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Add a silent audio sink to consume WebAudio data on silence detection.Min Qin2015-06-245-18/+123
| | | | | | | | | | | | | | | | | | | | | | | | The current android implementation of WebAudio is not power friendly. It holds the AudioMix wakelock, and causes a lot of battery consumption even if tab is backgrounded. When an AudioContext is created, WebAudio will start enqueueing data to the output device. This happens even when no data is decoded or no audio buffer is appended. This CL adds a SilentAudioSink to consume data when consecutive empty audio buffers are received. In the idle mode, the player will no longer enqueue data to the output device. It regularly check the received data and exits the idle mode if non-empty data are encountered. The intervals to check the data is calculated by the consumption time of the last received buffer. BUG=470153 TBR=dalecurtis Review URL: https://codereview.chromium.org/1195633003 Cr-Commit-Position: refs/heads/master@{#335799} (cherry picked from commit bda540eb1cbfd36dda3eec0206913331ca1ab822) Review URL: https://codereview.chromium.org/1209683003. Cr-Commit-Position: refs/branch-heads/2403@{#391} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Pin shortcuts via shell verbs rather than ShellExecuteEx.Greg Thompson2015-06-247-25/+105
| | | | | | | | | | | | | | | | | BUG=498383 TEST=Chrome's icon is pinned to the taskbar upon install on Win7, 8, 8.1, and 10. TBR=sky@chromium.org Review URL: https://codereview.chromium.org/1193363003 Cr-Commit-Position: refs/heads/master@{#335630} (cherry picked from commit fdeaa0e1d9ca6166b27e5f8ac19bba3a5ee9fcb2) TBR=grt@chromium.org Review URL: https://codereview.chromium.org/1207783002. Cr-Commit-Position: refs/branch-heads/2403@{#390} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Merge to M44: Suggest to fill password change formsVadym Doroshenko2015-06-2412-26/+186
| | | | | | | | | | | | | | | | | | This CL allows suggesting for filling password change forms for both username and password fields. We allow to fill password field without filling username to fix cases when a previous to the password text field is not username or invisible (e.g. facebook.com). TBR=gcasto@chromium.org BUG=359315 Review URL: https://codereview.chromium.org/1161023008 Cr-Commit-Position: refs/heads/master@{#335019} (cherry picked from commit f78d9b496ce4e04a10374b1bb0cf0013ac5716ba) Review URL: https://codereview.chromium.org/1210503003. Cr-Commit-Position: refs/branch-heads/2403@{#389} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Handle uninitialized loading timeJaekyun Seok2015-06-242-2/+20
| | | | | | | | | | | | | | | | | | | | For now, TabRedirectHandler doesn't handle the case of uninitialized loading time. So it can't process a navigation with uninitialized user interaction time when the loading time isn't initialized yet. BUG=503781 TBR=mariakhomenko@chromium.org,changwan@chromium.org Review URL: https://codereview.chromium.org/1202913003 Cr-Commit-Position: refs/heads/master@{#335848} (cherry picked from commit 4f5ac0ce405e02b90d8487a304ea1d2ccc4d7e25) Review URL: https://codereview.chromium.org/1203003002. Cr-Commit-Position: refs/branch-heads/2403@{#388} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Block an Intent navigation which is redirected from reloadingJaekyun Seok2015-06-243-2/+144
| | | | | | | | | | | | | | | BUG=496129 TBR=mariakhomenko@chromium.org Review URL: https://codereview.chromium.org/1193913008 Cr-Commit-Position: refs/heads/master@{#335615} (cherry picked from commit d7fae97a3ae0a39654db446384ea33206a2b6cfe) Review URL: https://codereview.chromium.org/1207503003. Cr-Commit-Position: refs/branch-heads/2403@{#387} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Incrementing VERSION to 44.0.2403.63chrome-tpm2015-06-241-1/+1
| | | | | Cr-Commit-Position: refs/branch-heads/2403@{#386} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* [Android FRE] Additional sign-in metricsRuslan Abdikeev2015-06-244-0/+45
| | | | | | | | | | | | | | | BUG=503312,450423 TBR=asvitkine@chromium.org Review URL: https://codereview.chromium.org/1200933003 Cr-Commit-Position: refs/heads/master@{#335791} (cherry picked from commit 05f3d37bc4ae390f44c38440b0081b77cf89b585) Review URL: https://codereview.chromium.org/1205703004. Cr-Commit-Position: refs/branch-heads/2403@{#385} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Incrementing VERSION to 44.0.2403.62chrome-tpm2015-06-241-1/+1
| | | | | Cr-Commit-Position: refs/branch-heads/2403@{#384} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Use page heap in in-process rendererBo Liu2015-06-232-8/+11
| | | | | | | | | | | | | | | | | | This reduces number of ashmem allocations on in-process webview, which prevents going over the file descriptor limit. BUG=503632, 503724 Review URL: https://codereview.chromium.org/1199243004 Cr-Commit-Position: refs/heads/master@{#335784} (cherry picked from commit 9760e2120fdbb57aecd8af44928d6a5949629810) TBR=boliu@chromium.org Review URL: https://codereview.chromium.org/1202823004. Cr-Commit-Position: refs/branch-heads/2403@{#383} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Close tray bubble before disabling UI for sign-in.Pavel Sergeev2015-06-231-1/+13
| | | | | | | | | | | | | | | | | | | | | | | | | During Chrome OS sign-in we temperoraly block the UI, to prevent user from interracting with UI elements, particullary with the system tray menu. However, if system tray menu is opened before disabling the UI, it remains opened after. Fixed this by closing the menu together with disabling the UI. BUG=497080 TEST=manually Review URL: https://codereview.chromium.org/1187593006 Cr-Commit-Position: refs/heads/master@{#335133} Review URL: https://codereview.chromium.org/1194053003 Cr-Commit-Position: refs/heads/master@{#335562} (cherry picked from commit 54491dc0ca9c5edbbc300e0e7cc56ad2beee3fe7) Review URL: https://codereview.chromium.org/1200383003. Cr-Commit-Position: refs/branch-heads/2403@{#382} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Fix location information in accessibility snapshotSelim Gurun2015-06-233-9/+27
| | | | | | | | | | | | | | BUG=502082 The location information needs to be corrected using page scale/dpi information.It should also use the correct location information when iframes are involved. Review URL: https://codereview.chromium.org/1191163002 (cherry picked from commit 8c19213ff00c4a221bd65453ce6cdb1a66bfea78) Cr-Original-Commit-Position: refs/heads/master@{#335435} Cr-Commit-Position: refs/branch-heads/2403@{#381} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Add UMA to track whether SERP was loaded when panel is closedTheresa Wellington2015-06-232-3/+23
| | | | | | | | | | | | | | | | | Add a ContextualSearch metric to track whether or not the SERP was loaded when the user closes an opened panel. BUG=501440 TBR=aurimas@chromium.org Review URL: https://codereview.chromium.org/1193563003 Cr-Commit-Position: refs/heads/master@{#335162} Review URL: https://codereview.chromium.org/1201283002. Cr-Commit-Position: refs/branch-heads/2403@{#380} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* [ios/web] Pass best-guess transition information with push stateStuart Morgan2015-06-234-16/+38
| | | | | | | | | | | | | | | | | | | | Use user interaction data to distinguish between link transitions and client redirect transitions for creating push state entries. This is to prevent the addition of extraneous history entries for push events that are redirects. BUG=496109 Review URL: https://codereview.chromium.org/1194123002 Cr-Commit-Position: refs/heads/master@{#335421} (cherry picked from commit c297675c2307e5082be98962a0a09b583442fe6b) TBR=eugenebut Review URL: https://codereview.chromium.org/1202713003. Cr-Commit-Position: refs/branch-heads/2403@{#379} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* branch 2403 fork: Drop gpu raster resources in android webviewBo Liu2015-06-231-0/+14
| | | | | | | | | | | | | | | | This is a more contained fork of the fix in https://codereview.chromium.org/1146313004 Drop gpu raster resources when webview memory is supposed to be released. BUG=502331 TBR=boliu@chromium.org Review URL: https://codereview.chromium.org/1200863003. Cr-Commit-Position: refs/branch-heads/2403@{#378} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Don't check for USE_CREDENTIALS permission on Android M.Jason Kersey2015-06-233-8/+16
| | | | | | | | | | | | BUG=501435 Review URL: https://codereview.chromium.org/1194423002 (cherry picked from commit d74b322a46041b6838b3e0f36c0489bc9bca8554) Cr-Original-Commit-Position: refs/heads/master@{#335585} Cr-Commit-Position: refs/branch-heads/2403@{#377} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
* Merge to M44: Files.app: Disable eject button on MTP device.Yuki Awano2015-06-231-1/+3
| | | | | | | | | | | | | | | | BUG=495997 TEST=manually tested; Connect MTP device and confirm that MTP volume does not have eject button. TBR=yoshiki@chromium.org Review URL: https://codereview.chromium.org/1148853004 Cr-Commit-Position: refs/heads/master@{#333233} (cherry picked from commit f0da152fd8af7961e00508e40ec0662f32dc8d5d) Review URL: https://codereview.chromium.org/1196243004. Cr-Commit-Position: refs/branch-heads/2403@{#376} Cr-Branched-From: f54b8097a9c45ed4ad308133d49f05325d6c5070-refs/heads/master@{#330231}
generated by cgit v1.1 at 2025-02-14 16:56:21 +0000