- 14 Mar, 2018 40 commits
-
-
Kent Tamura authored
This CL has no behavior changes. Bug: 770603 Change-Id: I919b422532b69ab4e25d6915a6b4db7bc8e3022f Reviewed-on: https://chromium-review.googlesource.com/961042Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#543032}
-
Tetsui Ohkubo authored
This CL ports unit tests from TrayTilesTest. Also this CL fixes DCHECK failures and crash in logged out state. UnifiedSystemTray design doc: go/cros-qs-restyling TEST=TopShortcutsViewTest(ash_unittests) BUG=none Change-Id: Id32540a3213866aa86b89025f1aa7bc97bae989b Reviewed-on: https://chromium-review.googlesource.com/958304Reviewed-by:
Yoshiki Iguchi <yoshiki@chromium.org> Commit-Queue: Tetsui Ohkubo <tetsui@chromium.org> Cr-Commit-Position: refs/heads/master@{#543031}
-
chrome://resources/*Daniel Cheng authored
Bug: 821613 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: Icdaab0eb77a72a7b6ad0c491424672614c24a9fa Reviewed-on: https://chromium-review.googlesource.com/961727Reviewed-by:
Raymes Khoury <raymes@chromium.org> Reviewed-by:
Sam McNally <sammc@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#543030}
-
Kunihiko Sakamoto authored
<link rel=preload> will play an important role in signed-exchange prefetching. This patch makes srcset/imgsizes on <link rel=preload> work with the SignedHTTPExchange flag too (in addition to the Experimental Web Platform features flag), so that people can easily try out it. Bug: 803774,813452 Change-Id: I976d007c73b9cb5459d35e0e178f8d8d90484709 Reviewed-on: https://chromium-review.googlesource.com/961627Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#543029}
-
Kunihiko Sakamoto authored
It takes at least 5 seconds. Marking it as SLOW to ensure that it runs with an increased timeout. NoTry: True Bug: 816026 Change-Id: Ie6923678e945b05def57f93647ae69a97190da86 Reviewed-on: https://chromium-review.googlesource.com/961922 Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org> Reviewed-by:
Takashi Toyoshima <toyoshim@chromium.org> Cr-Commit-Position: refs/heads/master@{#543028}
-
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/064937143390..456b0d648f72 $ git log 064937143..456b0d648 --date=short --no-merges --format='%ad %ae %s' 2018-03-13 iannucci [bot_update] Remove support for rietveld patches. Created with: roll-dep src/third_party/depot_tools The AutoRoll server is located here: https://depot-tools-chromium-roll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=agable@chromium.org Change-Id: I37991cf31009daa325d77a055f4a8f569fd86167 Reviewed-on: https://chromium-review.googlesource.com/961820Reviewed-by:
depot-tools-chromium-autoroll <depot-tools-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: depot-tools-chromium-autoroll <depot-tools-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#543027}
-
Hiroki Nakagawa authored
As a preparation for module loading support for workers, this CL does mainly 2 things: - This renames WorkletModuleScriptFetcher to WorkerOrWorkletModuleScriptFetcher, and WorkletModuleResponsesMapProxy to WorkerOrWorkletModuleFetchCoordinatorProxy. This enables workers can reuse worklets' module loading classes. - This introduces WorkerOrWorkletModuleFetchCoordinator interface. Implementation of the interface is expected to fetch module scripts via DocumentModuleScriptFetcher, to manage inflight requests, and to notify completions of the requests to WorkerOrWorkletModuleScriptFetcher on the worker thread. For worklets, WorkletModuleResponsesMap inherits the interface. For workers, following CLs introduce a new class, WorkerModuleFetchCoordinator, because WorkletModuleResponsesMap have custom fetch logic for caching and it's not reusable for workers. See the design doc for details: https://docs.google.com/document/d/1IMGWAK7Wq37mLehwkbysNRBBnhQBo3z2MbYyMkViEnY/edit#heading=h.637avx8i5qtn Bug: 680046 Change-Id: Iba7916bb9b5aefbc8c695ff9865bcbe756801412 Reviewed-on: https://chromium-review.googlesource.com/958801Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#543026}
-
Khushal authored
PaintOpReader::Read for SkData is used by 2 code-paths, deserializing SkTextBlobs and AnnotateOps. While AnnotateOp needs to copy the SkData, the copy for SkTextBlobs is completely unnecessary. This also uncovered skia caching keyed on text blob ids in GrAtlasTextContext, which we'll miss in OOP by re-serializing the text blobs each time. This should be addressed by caching these on the service side in a follow up. R=enne@chromium.org BUG: 821584 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel Change-Id: I77b47621e0f0bca225377968b02ca5f401804bc0 Reviewed-on: https://chromium-review.googlesource.com/959439 Commit-Queue: Khushal <khushalsagar@chromium.org> Reviewed-by:
enne <enne@chromium.org> Cr-Commit-Position: refs/heads/master@{#543025}
-
https://skia.googlesource.com/skia.git/+log/cefa808f3f23..d8853ec0fd01 $ git log cefa808f3..d8853ec0f --date=short --no-merges --format='%ad %ae %s' 2018-03-10 mtklein exact divide by 255 with NEON 2018-03-12 herb Cleanup size calculations in SkGlyph Created with: roll-dep src/third_party/skia The AutoRoll server is located here: https://autoroll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_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=stephana@chromium.org Change-Id: If8f831a0c5321b4d7e3d219b73968e573147e97c Reviewed-on: https://chromium-review.googlesource.com/961811Reviewed-by:
skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#543024}
-
Robert Iannucci authored
This way they can find psutil on dev machines as well as bots. R=skyostil@chromium.org, tikuta@chromium.org Bug: 821669 Change-Id: I7d53409ea9e62597f9edcea472dbec754d929687 Reviewed-on: https://chromium-review.googlesource.com/961863Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: Robbie Iannucci <iannucci@chromium.org> Cr-Commit-Position: refs/heads/master@{#543023}
-
Xiaocheng Hu authored
When calling ShowLineTreeForThis() on RootInlineBox and children- inline LayoutBlockFlow, the existing code searches for inline structures in a wrong LayoutBlock, which is the block container of the inline formatting context instead of the inline formatting context itself. This patch fixes the issue. Bug: 821289 Change-Id: Icba7ee2b036649df5caba75050b4267188a8dbda Reviewed-on: https://chromium-review.googlesource.com/961797Reviewed-by:
Koji Ishii <kojii@chromium.org> Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org> Cr-Commit-Position: refs/heads/master@{#543022}
-
Dale Curtis authored
When GMB copies fall behind we would previously also slow down the Decode() calls, after GMBDecoderWrapper was introduced we would return the DecodeCB while the copy was pending, letting DecodeStream think it could schedule another Decode. If decoding rate is higher than the copy rate, this will generate absurd amounts of decode results waiting for copying. This patch changes the behavior to be based on GetMaxDecodeRequests(); e.g., when GetMaxDecodeRequests() == 1, this allows another decode if there is at most 1 copy outstanding. When GMDR() == 2, this allows another decode if there are at most 2 copies outstanding. BUG=801245, 820167 TEST=new test and existing tests modified to enforce this. Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_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 Change-Id: I06415feda36643eb65aac69b17125737e12254c0 Reviewed-on: https://chromium-review.googlesource.com/959149Reviewed-by:
Xiaohan Wang <xhwang@chromium.org> Reviewed-by:
Daniele Castagna <dcastagna@chromium.org> Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/heads/master@{#543021}
-
Ramin Halavati authored
The script that traffic annotations FYI bot runs is changed to a new one that specifically checks network traffic annotation auditor's health. Bug: 690323 Change-Id: Iaa97d5ce27b2b9f9d2c523deae7fda803ffb5079 Reviewed-on: https://chromium-review.googlesource.com/955688Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Commit-Queue: Ramin Halavati <rhalavati@chromium.org> Cr-Commit-Position: refs/heads/master@{#543020}
-
Jinsuk Kim authored
With java WebContentsUserData in place, ContentViewCore doesn't have to rely on native to retrieve its java object. This CL refactors ContentViewCore so that it is backed by WebContentsUserData. Bug: 789000 Change-Id: Icf4b6b0e90e78cd8cfd4d7d74f1d14196736d2b5 Reviewed-on: https://chromium-review.googlesource.com/945035 Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Reviewed-by:
Luke Halliwell <halliwell@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#543019}
-
Morten Stenshorne authored
We cannot use the content size (intrinsic block size) as min-height or max-height (min-width or max-width, if writing mode is vertical). Doing so would cause min-height to incorrectly override any specified height or max-height that is less than the intrinsic block size, and max-height to override any specified height that's greater than the intrinsic block size. Do what the spec says [1] instead: max-height to become 'none', and min-height to become 0. This fixes the final rendering problem with Acid2 (this was about the min-height issue). It now renders correctly with LayoutNG! Since no other tests than Acid2 started to pass with this change, I wrote a couple. [1] https://www.w3.org/TR/CSS22/visudet.html#min-max-heights XXXXXX XX XX X X X O O X X X X /\ X X \/ X X X X X X X X XXXXXXXX X X X XX XX XXXXXX Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: Ic4f2c3c1dbc2bd66956ed4b270b08058999bc351 Reviewed-on: https://chromium-review.googlesource.com/960085Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Aleks Totic <atotic@chromium.org> Reviewed-by:
Emil A Eklund <eae@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#543018}
-
Siddhartha authored
There could be multiple providers. So, each must create allocator dumps with distinct names. Refer notes on GetOrCreateAllocatorDump. Group autocomplete and in_memory_url_index dumps under different child dumps for easier collection of metrics. BUG=803822 TBR=mpearson@chromium.org Change-Id: I872491bb1496572600fc6b6f87d9198a76eea8c7 Reviewed-on: https://chromium-review.googlesource.com/961263 Commit-Queue: Siddhartha S <ssid@chromium.org> Reviewed-by:
Justin Donnelly <jdonnelly@chromium.org> Cr-Commit-Position: refs/heads/master@{#543017}
-
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 The AutoRoll server is located here: https://afdo-chromium-roll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=gbiv@chromium.org Change-Id: I5e7f5a43bbf36e9e4cc5c81a31611fea17d95019 Reviewed-on: https://chromium-review.googlesource.com/961392 Commit-Queue: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#543016}
-
Hajime Hoshi authored
This is a retry of https://chromium-review.googlesource.com/c/chromium/src/+/908371, with fixing the DCHECK (NOTREACHED) error. We were not sure when the NOTREACHED is reached before the fix, but now this case becomes deterministic (see the discussion at crbug.com/816533) Note that this might still cause Telemetry regressions reported at crbug.com/753071 before, but this is expected. A document is leaked because AutofillAgent hold a lastly used element even after navigation happens, and the document of the element remains until a new (input) element is focused. This CL fixes this issue by resetting the element in AutofillAgent when navigation happens. Bug: 734427, 755489, 816533 Change-Id: I7eb2f9fb879d826297247c4c66e366ec0b73067c Reviewed-on: https://chromium-review.googlesource.com/939224Reviewed-by:
Sebastien Seguin-Gagnon <sebsg@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org> Cr-Commit-Position: refs/heads/master@{#543015}
-
Hayato Ito authored
The previous comment was added at [1], saying the code is suspicious, however, the code is correct. To avoid a confusion, update the comments. [1]: https://chromium-review.googlesource.com/c/chromium/src/+/755855 Change-Id: I9c30c53b6cd24e14160fa18b8fc0c3dc7aff2dc0 Reviewed-on: https://chromium-review.googlesource.com/959947 Commit-Queue: Hayato Ito <hayato@chromium.org> Reviewed-by:
Takayoshi Kochi <kochi@chromium.org> Cr-Commit-Position: refs/heads/master@{#543014}
-
Jinsuk Kim authored
pixels per mouse_scroll_wheel_tick was being set wrong (should have been wheel_scroll_factor but was the value divided by dip_scale was set), hence decreased the scroll rate and caused the regression. This CL fixes the issue. Now WindowAndroid stores wheel_scroll_factor (instead of tick multiplier) which is accessed much more often, for efficiency's sake. Bug: 821101 Change-Id: I99e81fdfc21ec101a99092c50555be4f429d7a20 Reviewed-on: https://chromium-review.googlesource.com/961503Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Cr-Commit-Position: refs/heads/master@{#543013}
-
Tsuyoshi Horo authored
Before this CL, SignedExchangeSignatureVerifier didn't verify date and expires values on the "Signature" HTTP header. This CL introduces SignedExchangeSignatureVerifier::VerifyTimestamps to verify those. The original CL http://crrev.com/c/923468 was created by kouhei@. Bug: 803774 Change-Id: I21a2db04c9bf80787226631696e1e334219bf893 Reviewed-on: https://chromium-review.googlesource.com/958368Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Commit-Queue: Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/master@{#543012}
-
https://chromium.googlesource.com/angle/angle.git/+log/690c8eb7f2d2..fccebffe63cf $ git log 690c8eb7f..fccebffe6 --date=short --no-merges --format='%ad %ae %s' 2018-03-08 jiawei.shao ES31: Support adjacency draw modes for geometry shader Created with: roll-dep src/third_party/angle The AutoRoll server is located here: https://angle-chromium-roll.skia.org Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_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=cwallez@chromium.org Change-Id: I4e61a9ad93a380b0f5ec8a392f95a154ce812590 Reviewed-on: https://chromium-review.googlesource.com/961813 Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#543011}
-
Kent Tamura authored
This CL has no behavior changes. Bug: 770603 Change-Id: Ieaeec84b67a6a4dbb0063e43478def41b909448f Reviewed-on: https://chromium-review.googlesource.com/961183 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#543010}
-
abhishek.a21 authored
Reference: https://docs.google.com/spreadsheets/d/1HKl-gMSzjI-ygRkYTvqpJRwSW0ZI-xj-0aoiNdTum2g/edit#gid=939250318 Change-Id: I160fcaaa9aca29ab5c78eda66a78be2c5775720f Reviewed-on: https://chromium-review.googlesource.com/956829Reviewed-by:
Roger McFarlane <rogerm@chromium.org> Reviewed-by:
Sanjoy Pal <sanjoy.pal@samsung.com> Commit-Queue: Abhishek Agarwal <abhishek.a21@samsung.com> Cr-Commit-Position: refs/heads/master@{#543009}
-
James Darpinian authored
There were three problems: 1. We didn't multiply the number of vertices by the number of instances. 2. We didn't account for vertices written by previous draw calls. 3. We didn't round the vertex count down to the nearest number of whole primitives. Fixes the WebGL 2 conformance test added here: https://github.com/KhronosGroup/WebGL/pull/2604 Bug: 820639 Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_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 Change-Id: I9566ad14aa6671eca127a1b7f68b73e6408acd10 Reviewed-on: https://chromium-review.googlesource.com/957743 Commit-Queue: James Darpinian <jdarpinian@chromium.org> Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#543008}
-
Koji Ishii authored
Following bot results are included. 4201 4203 4207 4211 4215 4216 1 lines were removed and 3 lines were deflaked by consecutive results since 4166. TBR=eae@chromium.org NOTRY=true Bug: 591099 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: I2885e853016e26861f8776a57aab36990ce8993c Reviewed-on: https://chromium-review.googlesource.com/960541 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#543007}
-
Kunihiko Sakamoto authored
Bug: 803774 Change-Id: Id7c04828f3a78401ff0e809bccfdcfd036473a6f Reviewed-on: https://chromium-review.googlesource.com/958945 Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#543006}
-
mark a. foltz authored
This updates the Media Router integration tests so they run in the Chromium waterfall with the open source Media Router component extension and its mock (test) Media Route Provider. Additional changes: - Removes extension from top level BUILD.gn as it is only used for browser tests at the moment. - Splits the targets for Media Router browser tests into integration tests (part of main browser_tests suite), e2e tests (which require the external component extension), perf tests, and shared support code. - Renames the "test" extension to the "telemetry" extension used for perf tests to avoid confusion. - Updates README files - One test is not compatible with the Chromium component and need to be fixed. Bugs 818767 filed for follow-up. Bug: 698796 Change-Id: I6cc9302ffd72de95630ce33ca3617b3b73b9e722 Reviewed-on: https://chromium-review.googlesource.com/917214 Commit-Queue: mark a. foltz <mfoltz@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Derek Cheng <imcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#543005}
-
Darren Shen authored
This patch adds support for scroll-margin-* and adds relevant tests. Spec: https://drafts.csswg.org/css-scroll-snap-1/#margin-longhands-physical Bug: 820299 Change-Id: I46f8482c88c237de2a9d263b3a334ac9c03f4fca Reviewed-on: https://chromium-review.googlesource.com/958755Reviewed-by:
nainar <nainar@chromium.org> Commit-Queue: Darren Shen <shend@chromium.org> Cr-Commit-Position: refs/heads/master@{#543004}
-
Ran Ji authored
Change-Id: Ibae84f3215ae29e2154df538f4ff7e86f72118b5 Reviewed-on: https://chromium-review.googlesource.com/959750 Commit-Queue: Ran Ji <ranj@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#543003}
-
Kent Tamura authored
This CL has no behavior changes. Bug: 770603 Change-Id: I7229bd5cb53d468c054d323a458fb78ca0803535 Reviewed-on: https://chromium-review.googlesource.com/961164 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Cr-Commit-Position: refs/heads/master@{#543002}
-
Evan Stade authored
Bug: none Change-Id: I4bf6dc8b898a5c0af1516888e40e290e5bf91d95 Reviewed-on: https://chromium-review.googlesource.com/960982Reviewed-by:
James Cook <jamescook@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#543001}
-
chrome://flags/#enable-signed-http-exchangeTsuyoshi Horo authored
Bug: 803774 Change-Id: I0cc2bbcdb34ef09f4f0fbcfeefe2d667bfec1cd8 Reviewed-on: https://chromium-review.googlesource.com/930645Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Tsuyoshi Horo <horo@chromium.org> Cr-Commit-Position: refs/heads/master@{#543000}
-
Jinsuk Kim authored
Now we got only a handful of references to ContentViewCore object left in RenderWidgetHostViewAndroid. All but 3 are all null checks trying to see if content_view_core_ is set to null or not, which is equivalent to checking if the native view (ViewAndroid) of ContentViewCore and its own native view form a view tree or not. This can be replaced simply by a boolean flag. The only 3 are significant (i.e. invoking methods of CVC) ContentViewCore::GetViewAndroid() - RWHVA may not have an access to the parent native view. It should be passed to RWHVA instead. ContentViewCore::RequestDisallowInterceptTouchEvent() - It goes up to Java container view to invoke android.view.View.requestDisallowInterceptTouchEvent. One more move from CVC to ViewAndroidDelegate... ContentViewCore::GetWindowAndroid() : same WindowAndroid (or null if not attached to view tree) can be obtained via ViewAndroid::GetWindowAndroid(). Bug: 626765 Change-Id: I80088c6a9ca2ca0047184ac77f84f08f64ff0acb Reviewed-on: https://chromium-review.googlesource.com/958646 Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#542999}
-
Kent Tamura authored
This CL has no behavior changes. Bug: 770603 Change-Id: I3d8a6c2813b360ca5497f9d8bc31e8e6e2c6caf0 Reviewed-on: https://chromium-review.googlesource.com/961166 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Cr-Commit-Position: refs/heads/master@{#542998}
-
Keishi Hattori authored
Split GCType into MarkingType and SweepingType so we can track if the gc was incremental marking or not. Change-Id: I2264badba6b0e7dbdbd41e2bb4958ca3fb37cb0d Reviewed-on: https://chromium-review.googlesource.com/958898Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Keishi Hattori <keishi@chromium.org> Cr-Commit-Position: refs/heads/master@{#542997}
-
Kent Tamura authored
This CL has no behavior changes. Bug: 770603 Change-Id: I0c1872dc6942c3cccf706b4c60869402bbe47f59 Reviewed-on: https://chromium-review.googlesource.com/961561 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Cr-Commit-Position: refs/heads/master@{#542996}
-
chrome://flags/#force-ui-directionSidney San Martín authored
Bug: 820348 Change-Id: Id9c8ff9878f6595f99d4630a18aa023b55cc8467 Reviewed-on: https://chromium-review.googlesource.com/956297Reviewed-by:
Jungshik Shin <jshin@chromium.org> Reviewed-by:
Leonard Grey <lgrey@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Sidney San Martín <sdy@chromium.org> Cr-Commit-Position: refs/heads/master@{#542995}
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=govind@chromium.org Change-Id: I63fded1b83f7f2fd51ca455f2b1f5eefee8f76d4 Reviewed-on: https://chromium-review.googlesource.com/961809Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#542994}
-
Kent Tamura authored
This CL has no behavior changes. Bug: 770603 Change-Id: I2084d2a10cf69f2815c147769d46d8a5f0cba7ff Reviewed-on: https://chromium-review.googlesource.com/961621 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#542993}
-