GitLab

Currently we don't have any real uses of proguard in non-internal code. This
makes it really easy to break the proguard rules.

This enables proguard for ChromeShell with a fairly conservative configuration
(for example, everything in org.chromium.** is kept).

Review URL: https://codereview.chromium.org/1107653003

Cr-Commit-Position: refs/heads/master@{#327547}

R=tommycli@chromium.org,bauerb@chromium.org
BUG=478918

Review URL: https://codereview.chromium.org/1112723002

Cr-Commit-Position: refs/heads/master@{#327546}

Working on trimming down plugin warnings on the Windows clang build.

BUG=467287
TBR=dalecurtis@chromium.org

Review URL: https://codereview.chromium.org/1118573002

Cr-Commit-Position: refs/heads/master@{#327545}

Need to move this logic out so that we can get the icon earlier in the
shortcut adding process.

BUG=457424

Review URL: https://codereview.chromium.org/1103273011

Cr-Commit-Position: refs/heads/master@{#327544}

The code requires methods only present on 10.5+, so having a deployment target
of 10.4 is incorrect.

BUG=471823

Review URL: https://codereview.chromium.org/1112753002

Cr-Commit-Position: refs/heads/master@{#327543}

Working on trimming down plugin warnings on the Windows clang build.

BUG=467287

Review URL: https://codereview.chromium.org/1110783003

Cr-Commit-Position: refs/heads/master@{#327542}

This cl adds a key sequence that enables ChromeVox Next. Eventually, this can turn into a proper option.

TEST=open ChromeVox options page, type 'n', 'e', 'x', 't'. Observe message and ChromeVox Next is enabled on all newly opened tabs.

Review URL: https://codereview.chromium.org/1107343006

Cr-Commit-Position: refs/heads/master@{#327541}

Includes:
0bb67471bca068996e15b56738fa4824dfa19de0 Slightly better docs for git instead of svn
8866260996c063f514dfafd0e05743a42709a49c win: prefer amd64_x86 compiler on >= 2013, not just 2013
3601f26003c6163128a66330ce845b5cb309c7a9 Make dump_dependency_json.py write <| list files to the output directory
2f66a3f949530074bc5151ea8daf6c2b7abd07a7 Whitespace change to test the new GYP waterfalls.

TBR=dpranke@chromium.org
BUG=482238

Review URL: https://codereview.chromium.org/1113863002

Cr-Commit-Position: refs/heads/master@{#327540}

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/61f501f..3596482

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
TBR=humper@google.com

Review URL: https://codereview.chromium.org/1111333004

Cr-Commit-Position: refs/heads/master@{#327539}

BUG=471823

Review URL: https://codereview.chromium.org/1117513002

Cr-Commit-Position: refs/heads/master@{#327538}

in support of https://codereview.chromium.org/986353002/

BUG=

Review URL: https://codereview.chromium.org/1115713003

Cr-Commit-Position: refs/heads/master@{#327537}

BUG=481919
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:linux_perf_bisect;tryserver.chromium.perf:mac_perf_bisect;tryserver.chromium.perf:android_nexus5_perf_bisect

Review URL: https://codereview.chromium.org/1112553002

Cr-Commit-Position: refs/heads/master@{#327536}

This fixes many tests in content_unittests and content_browsertests.

BUG=439423, 470082, 475027

Review URL: https://codereview.chromium.org/1108283002

Cr-Commit-Position: refs/heads/master@{#327535}

The method -accessibilityChildren was introduced in the
NSAccessibilityLayoutArea protocol in Yosemite. To avoid confusion, I renamed
the method on TabStripView to tabStripViewAccessibilityChildren.

BUG=471823

Review URL: https://codereview.chromium.org/1111953003

Cr-Commit-Position: refs/heads/master@{#327534}

The target was removed in:
  https://codereview.chromium.org/1091513005
The tests are now part of mojo_shell_unittests.
The valgrind bots don't seem to build or run this target...

TODO: Make Valgrind build and run more mojo tests?

BUG=416620
TEST=No valgrind failures.
R=thestig@chromium.org

Review URL: https://codereview.chromium.org/1109283002

Cr-Commit-Position: refs/heads/master@{#327533}

BUG=482310
TBR=piman@chromium.org

Review URL: https://codereview.chromium.org/1115013002

Cr-Commit-Position: refs/heads/master@{#327532}

Depends on the Blink change: https://codereview.chromium.org/1092193003/

BUG=459008

Review URL: https://codereview.chromium.org/1084293004

Cr-Commit-Position: refs/heads/master@{#327531}

BUG=465594

Review URL: https://codereview.chromium.org/1110843002

Cr-Commit-Position: refs/heads/master@{#327530}

When a timezone is changed by a user at the OS level,
the ICU's default timezone has to be updated in both browser
and renderer processes.

This CL propagates the new timezone id to renderers as well as updating
it in the browser process.

A v8-side change is still necessary to get Intl.DateTimeFormat to
work in a new timezone.

BUG=406382,379595
TEST=Manual test (browser process). 1. Go to history page 2. Change the OS tz 3. Reload the history page and see if the timestamp is in a new timezone.

Review URL: https://codereview.chromium.org/697203006

Cr-Commit-Position: refs/heads/master@{#327529}

(And mark to gypi owners)

TBR=mark@chromium.org

Review URL: https://codereview.chromium.org/1119503002

Cr-Commit-Position: refs/heads/master@{#327528}

In order to allow sharing the DRM connection between browser and GPU
process, we need to be able to recover from GPU crashes and gracefully
handle page flipping events that were meant for the previous GPU
process.

BUG=445773

Review URL: https://codereview.chromium.org/1056793007

Cr-Commit-Position: refs/heads/master@{#327527}

fullscreen state test is flaky on mac. disable it.
This test does create window with fullscreen state.

BUG=482433

Review URL: https://codereview.chromium.org/1111333003

Cr-Commit-Position: refs/heads/master@{#327526}

-layout is the name of a method on NSView that performs constraint based
layout. The new method's name is -layoutEntryView.

BUG=471823

Review URL: https://codereview.chromium.org/1114743002

Cr-Commit-Position: refs/heads/master@{#327525}

Add ios/chrome/ios_strings_resources_${locale}.pak files to the
repack_locales.py script and "packed_resources" target.

BUG=475514

Review URL: https://codereview.chromium.org/1111823002

Cr-Commit-Position: refs/heads/master@{#327524}

We are now normifying extension enum property names as part of crbug.com/463184.
Update the extern generator to share this same pattern.

BUG=469920

Review URL: https://codereview.chromium.org/1109793003

Cr-Commit-Position: refs/heads/master@{#327523}

On pre-L devices, each item in the list of search engines had too much
top padding and no bottom padding. Also, on all devices, clicking a
search engine didn't show a ripple or highlight. Both of these bugs have
been fixed.

BUG=482193

Review URL: https://codereview.chromium.org/1109263004

Cr-Commit-Position: refs/heads/master@{#327522}

R=scottmg@chromium.org, mark@chromium.org
BUG=354261
CQ_EXTRA_TRYBOTS=tryserver.chromium.win:win8_chromium_gn_rel,win8_chromium_gn_dbg,win_chromium_gn_x64_rel,win_chromium_gn_x64_dbg

Review URL: https://codereview.chromium.org/1115533002

Cr-Commit-Position: refs/heads/master@{#327521}

In order for us to map and track between the touch events and their ACKs,
we need to set unique_event_id to WebTouchEvent when converting from TouchEvent.

This patch is part of a series:

patch #1: https://codereview.chromium.org/1008573002/
patch #2: This CL

BUG=466711

Review URL: https://codereview.chromium.org/999423003

Cr-Commit-Position: refs/heads/master@{#327520}

This regressed recently with the transition to the View-based
pull-to-refresh implementation. Restore the proper behavior which is
to suppress pull-to-refresh for fullscreen HTML5 scenarios.

BUG=435732

Review URL: https://codereview.chromium.org/1084533004

Cr-Commit-Position: refs/heads/master@{#327519}

Removes special initialization of the primary DRM device from
the GPU process. This allows us to work around sandboxing issues
on initialization on ARM devices since the DRM card devices will
all be sent to the sandboxed GPU via IPCs.

BUG=477792, 476728

Review URL: https://codereview.chromium.org/1100973002

Cr-Commit-Position: refs/heads/master@{#327518}

This CL combined rdsmith@'s CL(747453004) and mef@'s
CL(1073193002), and added tests to make sure sdch works for
both the old and the new API.

BUG=414885

Review URL: https://codereview.chromium.org/1085903002

Cr-Commit-Position: refs/heads/master@{#327517}

BUG=chromium:482180
TEST=None

Review URL: https://codereview.chromium.org/1118473004

Cr-Commit-Position: refs/heads/master@{#327516}

Turns out, Handle is just an alias for Local:
https://chromium.googlesource.com/v8/v8.git/+/master/include/v8.h#334

BUG=424445
R=scheib@chromium.org

Review URL: https://codereview.chromium.org/1115563002

Cr-Commit-Position: refs/heads/master@{#327515}

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/385e88c..61f501f

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
TBR=humper@google.com

Review URL: https://codereview.chromium.org/1114973003

Cr-Commit-Position: refs/heads/master@{#327514}

TBR=dmazzoni@chromium.org

Review URL: https://codereview.chromium.org/1113843002

Cr-Commit-Position: refs/heads/master@{#327513}

Replace usage of MessageLoopProxy under base/ with SingleThreadTaskRunner
and ThreadTaskRunnerHandle (excluding the implementation of MessageLoopProxy
itself which will removed later).

This patch was mostly autogenerated with
https://codereview.chromium.org/1010073002.

Depends on https://codereview.chromium.org/1086733002/.

BUG=465354
TBR=nkostylev@chromium.org,pkasting@chromium.org,pauljensen@chromium.org

Review URL: https://codereview.chromium.org/1100773004

Cr-Commit-Position: refs/heads/master@{#327512}

MessageLoopProxy is deprecated.
This basically does a search and replace:

MessageLoopProxy::current() -> ThreadTaskRunnerHandle::Get().

MessageLoopProxy -> SingleThreadTaskRunner

BUG=391045

Review URL: https://codereview.chromium.org/1108913006

Cr-Commit-Position: refs/heads/master@{#327511}

This change adds a test class for SyncCustomizationFragment.
Common code between this new class and SyncTest has been split
out into SyncTestBase. Everything else in this CL is fixing various
bugs that popped up when I tried to run the test.

BUG=480604

Review URL: https://codereview.chromium.org/1060373004

Cr-Commit-Position: refs/heads/master@{#327510}

The current Error Console UI is a little lacking. Most egregiously, there's no
way to clear errors. Update the UI by moving more of the error console into its
dedicated overlay, which
- Minimizes its footprint on the main page.
- Makes it easy to switch between errors easily.
Additionally, add support for removing specific (or all) errors associated with
extensions.

Screenshots are up at
https://drive.google.com/open?id=0BxjK6_MzZ8UPfndZcElPVGxxdWxXQmN3WkVtSFhNUkN3SlFVYVQtaGlpWTJaOU52YTRfOGs&authuser=0
(Internal only for now; will post externally soon)

BUG=482526

Review URL: https://codereview.chromium.org/1016413004

Cr-Commit-Position: refs/heads/master@{#327509}

Review URL: https://codereview.chromium.org/1111153002

Cr-Commit-Position: refs/heads/master@{#327508}