| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Adds paper-fab, paper-toolbar and polymer/layout, which are required by
the material PDF viewer. Also adds required files from existing
components to polymer_resources.
BUG=482793
Review URL: https://codereview.chromium.org/1140583003
Cr-Commit-Position: refs/heads/master@{#329787}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Noteworthy in this roll is that InterfacePtrs may no longer be
bound-to or passed-as simple pipe handles, but instead as
InterfacePtrInfos. This requires updating several call sites
of InterfacePtr's Bind and PassMessagePipe.
BUG=
TBR=ben@chromium.org
Review URL: https://codereview.chromium.org/1127293003
Cr-Commit-Position: refs/heads/master@{#329783}
|
|
|
|
|
|
|
|
|
| |
TBR=
BUG=
Review URL: https://codereview.chromium.org/1140093004
Cr-Commit-Position: refs/heads/master@{#329779}
|
|
|
|
|
|
|
|
|
|
| |
For example:
- third_party/ffmpeg/libavcodec/arm/hpeldsp_arm.S
- third_party/ffmpeg/libavcodec/x86/xvididct.asm
Review URL: https://codereview.chromium.org/1135243005
Cr-Commit-Position: refs/heads/master@{#329775}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
chrome_extensions.js: be4926041286f314d648ab5f3fcce5721693e602 -> ca37fefd29fef41fa481685c4b3398ba6ad10b8d
Also manually added networkingPrivate.onDeviceStateListChanged while it
makes its way to the github externs (to fix compile).
TBR=
BUG=
Review URL: https://codereview.chromium.org/1134693004
Cr-Commit-Position: refs/heads/master@{#329767}
|
|
|
|
|
|
|
|
| |
BUG=
Review URL: https://codereview.chromium.org/1131713006
Cr-Commit-Position: refs/heads/master@{#329698}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
WebRTC 9174:9187
Changes: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+log/8052935..65d8695
Libjingle 9171:9186
Changes: https://chromium.googlesource.com/external/webrtc/trunk/talk.git/+log/16f9a02..a8c7824
TBR=
BUG=
Review URL: https://codereview.chromium.org/1135393004
Cr-Commit-Position: refs/heads/master@{#329656}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary of changes available at:
https://boringssl.googlesource.com/boringssl/+log/68de407..771a138
This also removes update_gypi_and_asm.py in favor of the script inside
BoringSSL proper.
BUG=none
Review URL: https://codereview.chromium.org/1136743004
Cr-Commit-Position: refs/heads/master@{#329652}
|
|
|
|
|
|
|
|
| |
BUG=
Review URL: https://codereview.chromium.org/1134013004
Cr-Commit-Position: refs/heads/master@{#329596}
|
|
|
|
|
|
|
|
|
|
| |
This clobbers --extra_annotation_names in compile.py.
BUG=
Review URL: https://codereview.chromium.org/1140593003
Cr-Commit-Position: refs/heads/master@{#329534}
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=
NOTRY=true
NOTREECHECKS=true
Review URL: https://codereview.chromium.org/1140823005
Cr-Commit-Position: refs/heads/master@{#329515}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
id:40001 of https://codereview.chromium.org/1132443004/)
Reason for revert:
http://build.chromium.org/p/chromium.linux/builders/Android%20Arm64%20Builder%20%28dbg%29/builds/17339
Decent chance this will need to be re-uploaded manually, but let's see...
Original issue's description:
> Roll src/third_party/boringssl/src 68de407:de12d6c
>
> Summary of changes available at:
> https://boringssl.googlesource.com/boringssl/+log/68de407..de12d6c
>
> This also removes update_gypi_and_asm.py in favor of the script inside
> BoringSSL proper.
>
> BUG=none
>
> Committed: https://crrev.com/45248985036de1238c29d195b583797319a7020f
> Cr-Commit-Position: refs/heads/master@{#329500}
TBR=agl@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=none
Review URL: https://codereview.chromium.org/1128293004
Cr-Commit-Position: refs/heads/master@{#329504}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary of changes available at:
https://boringssl.googlesource.com/boringssl/+log/68de407..de12d6c
This also removes update_gypi_and_asm.py in favor of the script inside
BoringSSL proper.
BUG=none
Review URL: https://codereview.chromium.org/1132443004
Cr-Commit-Position: refs/heads/master@{#329500}
|
|
|
|
|
|
|
|
|
|
| |
Note that I did not add the checkbox compiled_resources.gyp to third_party/closure_compiler/compiled_resources.gyp because there are still some errors to dig through.
BUG=486240
Review URL: https://codereview.chromium.org/1112403006
Cr-Commit-Position: refs/heads/master@{#329476}
|
|
|
|
|
|
|
|
|
|
| |
This brings paper-icon-button v0.8.0 into third_party/polymer/v0_8.
BUG=485381
Review URL: https://codereview.chromium.org/1136293002
Cr-Commit-Position: refs/heads/master@{#329474}
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This brings paper-item v0.8.2 into third_party/polymer/v0_8.
I got a presubmit warning about not updating README.chromium.
Will that actually be a problem in the CQ?
BUG=485381
Review URL: https://codereview.chromium.org/1124133004
Cr-Commit-Position: refs/heads/master@{#329464}
|
|
|
|
|
|
|
|
| |
BUG=486240
Review URL: https://codereview.chromium.org/1136093004
Cr-Commit-Position: refs/heads/master@{#329460}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
unit tests on each continous build.
build/ CL: https://codereview.chromium.org/1128313003
R=tbreisacher@chromium.org
BUG=393873
NOTRY=true
Review URL: https://codereview.chromium.org/1137933003
Cr-Commit-Position: refs/heads/master@{#329450}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rather than having a file that must be kept current with all changes to
third_party/qcms/src highlight in the README.Chromium how the changes
since the import can be readily seen.
R=noel@chromium.org
BUG=None
TEST=None
Review URL: https://codereview.chromium.org/1136283002
Cr-Commit-Position: refs/heads/master@{#329431}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
WebRTC 9146:9174
Changes: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+log/6e78b8f..8052935
Libjingle 9147:9171
Changes: https://chromium.googlesource.com/external/webrtc/trunk/talk.git/+log/63f5a59..16f9a02
TBR=
BUG=
Review URL: https://codereview.chromium.org/1135213002
Cr-Commit-Position: refs/heads/master@{#329384}
|
|
|
|
|
|
|
|
| |
BUG=
Review URL: https://codereview.chromium.org/1129293003
Cr-Commit-Position: refs/heads/master@{#329357}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
SchemeIsCryptographic().
We recently introduced SchemeIsCryptographic() and IsOriginSecure(),
which are meant to replace SchemeIsSecure().
IsOriginSecure() roughly means "do we trust this content not to be
tampered with before it reaches the user?" [1] This is a higher-level
definition that corresponds to the new "privileged contexts" spec. [2]
SchemeIsCryptographic() [3] is close to the old definition of
SchemeIsSecure(), and literally just checks if the scheme is a
cryptographic scheme (HTTPS or WSS as of right now). The difference is
that SchemeIsCryptographic() will not consider filesystem URLs secure.
IsOriginSecure() should be correct for most Fizz code.
[1] https://code.google.com/p/chromium/codesearch#chromium/src/content/public/common/origin_util.h&sq=package:chromium&type=cs&l=19&rcl=143099866
[2] https://www.chromium.org/Home/chromium-security/prefer-secure-origins-for-powerful-new-features and https://w3c.github.io/webappsec/specs/powerfulfeatures/
[3] https://code.google.com/p/chromium/codesearch#chromium/src/url/gurl.h&sq=package:chromium&type=cs&l=250&rcl=1430998666
BUG=362214
Review URL: https://codereview.chromium.org/1136643004
Cr-Commit-Position: refs/heads/master@{#329310}
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The C++ define OFFICIAL_BUILD wasn't getting set, and the widevine version .rc files was getting linked twice.
CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:android_chromium_gn_compile_dbg,android_chromium_gn_compile_rel;tryserver.chromium.win:win8_chromium_gn_rel,win8_chromium_gn_dbg;tryserver.chromium.mac:mac_chromium_gn_rel,mac_chromium_gn_dbg
R=dpranke
TBR=ddorwin@chromium.org
Review URL: https://codereview.chromium.org/1134623003
Cr-Commit-Position: refs/heads/master@{#329308}
|
|
|
|
|
|
|
|
|
|
| |
Update to newer version (closure dependencies have been removed).
BUG=485567
Review URL: https://codereview.chromium.org/1138123002
Cr-Commit-Position: refs/heads/master@{#329297}
|
|
|
|
|
|
|
|
|
|
| |
See https://docs.google.com/document/d/1vapDN-76XS4dLsNRFQP9NMnhDstPAC88vPuKblhgMok/edit?usp=sharing for details.
BUG=485227
Review URL: https://codereview.chromium.org/1128203005
Cr-Commit-Position: refs/heads/master@{#329204}
|
|
|
|
|
|
|
|
|
| |
BUG=480679
TEST=manually tested as described in the issue; google_apis_unittests: DriveApiUrlGeneratorTest
Review URL: https://codereview.chromium.org/1125353003
Cr-Commit-Position: refs/heads/master@{#329139}
|
|
|
|
|
|
|
|
|
| |
TEST=unit_tests: *ProvidersModel* + tested manually.
BUG=74146
Review URL: https://codereview.chromium.org/1130393002
Cr-Commit-Position: refs/heads/master@{#329095}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
id:20001 of https://codereview.chromium.org/1122423007/)
Reason for revert:
http://build.chromium.org/p/chromium.linux/builders/Android%20Clang%20Builder%20%28dbg%29/builds/59288
Looks like the __STDC_FORMAT_MACROS thing got lost when inttypes.h and BN_FMT_* were moved to a public header. That it's a public header is... problematic...
Original issue's description:
> Roll src/third_party/boringssl/src 68de407:65a7e94
>
> Summary of changes available at:
> https://boringssl.googlesource.com/boringssl/+log/68de407..65a7e94
>
> This also removes update_gypi_and_asm.py in favor of the script inside
> BoringSSL proper.
>
> BUG=none
>
> Committed: https://crrev.com/c80637399c13d7c3e8cb7a16bd5de104feb449e9
> Cr-Commit-Position: refs/heads/master@{#329032}
TBR=agl@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=none
Review URL: https://codereview.chromium.org/1132243002
Cr-Commit-Position: refs/heads/master@{#329035}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary of changes available at:
https://boringssl.googlesource.com/boringssl/+log/68de407..65a7e94
This also removes update_gypi_and_asm.py in favor of the script inside
BoringSSL proper.
BUG=none
Review URL: https://codereview.chromium.org/1122423007
Cr-Commit-Position: refs/heads/master@{#329032}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The recently added --js_output_file seems to write output even if
there's a compile error (surprising to me, but I'm not totally sure what
should happen). This results in compile errors only failing on the bots
once (as when they're run again, nothing is rebuilt).
So I'm adding code to remove the output file when there's errors (for
now). This seems slightly better than writing the file to a temporary
location and moving it to the right location in the common case that
everything typechecks cleanly.
R=tbreisacher@chromium.org,twellington@chromium.org
BUG=486093
NOTRY=true
NOTREECHECKS=true
Review URL: https://codereview.chromium.org/1131343002
Cr-Commit-Position: refs/heads/master@{#329026}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will replace usage in c/b/r/settings/routing.
BUG=485381
Disabling presubmit due to errors with "=====" in README.md files.
NOPRESUBMIT=true
Review URL: https://codereview.chromium.org/1132583003
Cr-Commit-Position: refs/heads/master@{#328982}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a reasonable limit on the size of the vcgt to permit; this will
prevent rogue data potentially causing an OOM situation.
TEST=With test file blue-vcgt-test-color-profile-1024.icc observe that
the vcgt data is parsed and made available through the API but with
blue-vcgt-test-color-profile-2048.icc the vcgt is ignored.
R=noel@chromium.org
BUG=471749
Review URL: https://codereview.chromium.org/1138473002
Cr-Commit-Position: refs/heads/master@{#328966}
|
|
|
|
| |
Cr-Commit-Position: refs/heads/master@{#328844}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the user cancels a refresh via the report form warning dialog, we
never get a callback that the page has been reloaded. Consequently,
for gesture-triggered reloads the refresh spinner would continue showing
after the reload cancellation.
Instead, simply cancel the refresh animation when the repost warning
dialog is shown. This avoids any associated callback guarantee issues
while also preventing animation jank as the dialog is shown.
Also set the MaterialProgressDrawable animation's repeat count back to
infinite, instead relying on the SwipeRefreshHandler container to
terminate the refresh animation after a reasonable upper limit.
BUG=485609
Review URL: https://codereview.chromium.org/1131903003
Cr-Commit-Position: refs/heads/master@{#328825}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This way subclasses can specialize and then invoke ApplicationImpl's
implementation.
This is a merge of https://codereview.chromium.org/1129083002/ . I'm
TRBing as you already reviewed that one.
R=davemoore@chromium.org
TBR=davemoore@chromium.org
BUG=none
TEST=none
Review URL: https://codereview.chromium.org/1136553002
Cr-Commit-Position: refs/heads/master@{#328782}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
WebRTC 9128:9146
Changes: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+log/0d778c6..6e78b8f
Libjingle 9127:9147
Changes: https://chromium.googlesource.com/external/webrtc/trunk/talk.git/+log/0ff79d5..63f5a59
TBR=tommi
Review URL: https://codereview.chromium.org/1136433002
Cr-Commit-Position: refs/heads/master@{#328737}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After this, the next step will be to stop pulling hunspell in
third_party/hunspell through DEPS.
Removed the dependency on hunspell from chrome/browser/chromeos and chrome/browser/ui. Nothing in those places include from third_party/hunspell, so this dependency is not necessary and thus dropped.
BUG=472897
R=brettw@chromium.org
TBR=phajdan.jr@chromium.org # for checklicenses
Review URL: https://codereview.chromium.org/1121793003
Cr-Commit-Position: refs/heads/master@{#328719}
|
|
|
|
|
|
|
|
|
|
| |
Also add rfevang@ and noyau@ .
BUG=476996
Review URL: https://codereview.chromium.org/1123363005
Cr-Commit-Position: refs/heads/master@{#328652}
|
|
|
|
|
|
|
|
|
|
|
|
| |
Cherry-pick several recent changes to SwipeRefreshLayout and its
dependencies. This includes both several stylistic tweaks as well as a
fix for animation transitions on several devices.
BUG=485145
Review URL: https://codereview.chromium.org/1127193002
Cr-Commit-Position: refs/heads/master@{#328559}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This re-lands fixes for problems handling HeapWalk().
This also fixes several other bugs:
https://github.com/DynamoRIO/dynamorio/issues/1690,
https://github.com/DynamoRIO/drmemory/issues/1718,
https://github.com/DynamoRIO/drmemory/issues/1722, and
https://github.com/DynamoRIO/drmemory/issues/1723.
BUG=481231
TBR=thakis@chromium.org
NOTRY=true
Review URL: https://codereview.chromium.org/1128923003
Cr-Commit-Position: refs/heads/master@{#328548}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change removes the outer loop surrounding the core of the vcgt
parser that reads the table by multiplying the inner loops iterations
by the channel count (3.)
Minor: also update google.patch after last revision in
https://codereview.chromium.org/1050923006
R=noel@chromium.org
BUG=471749
TEST=Using a manual test program observe that test ICC file,
blue-vcgt-test-color-profile.icc, is parsed correctly.
Review URL: https://codereview.chromium.org/1129513004
Cr-Commit-Position: refs/heads/master@{#328515}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a registration flag for marking a pref as "lossy". There is no strict
time guarantee on when a lossy pref will be persisted to permanent storage when
it is modified.
WriteablePrefStore::PrefWriteFlags are introduced to be used to change the way
that prefs get written into a WriteablePrefStore.
The plumbing to pass registration flags down from PrefService into the
WriteablePrefStore and convert them into PrefWriteFlags is also added here.
The code which actually makes the pref behave in a lossy way has not been
added yet.
BUG=476800
Review URL: https://codereview.chromium.org/1092223004
Cr-Commit-Position: refs/heads/master@{#328481}
|
|
|
|
|
|
|
|
| |
BUG=479306
Review URL: https://codereview.chromium.org/1111473002
Cr-Commit-Position: refs/heads/master@{#328473}
|
|
|
|
|
|
|
|
| |
Also add missing dependency in mandoline.
Review URL: https://codereview.chromium.org/1126703005
Cr-Commit-Position: refs/heads/master@{#328396}
|
|
|
|
|
|
|
|
| |
This dependency has not used used since we removed pyauto (r261229).
Review URL: https://codereview.chromium.org/1122803003
Cr-Commit-Position: refs/heads/master@{#328324}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Switch all Android builds to use libc++ instead of stlport.
This change originally landed in crrev.com/315085, but was reverted in
crrev.com/315174 due to CQ execution time regressions.
The root cause of the test time regression was determined to be an issue
with MD5 hash computation, where hashing failed to produce a consistent
result in turn preventing deployment optimizations. This was resolved in
crbug.com/456396, leaving libc++ test runs comparable with stlport runs.
BUG=456396,427718
Review URL: https://codereview.chromium.org/951983002
Cr-Commit-Position: refs/heads/master@{#328296}
|
|
|
|
|
|
|
|
|
| |
TBR=tbreisacher@chromium.org
BUG=393873
Review URL: https://codereview.chromium.org/1122953002
Cr-Commit-Position: refs/heads/master@{#328273}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://codereview.chromium.org/1118223003/
Also import the right module (/facepalm). Checker.py got renamed
to compile.py recently. Still had a checker.pyc on my computer :(.
R=tbreisacher@chromium.org
BUG=393873
NOTREECHECKS=true
NOTRY=true
Review URL: https://codereview.chromium.org/1123803004
Cr-Commit-Position: refs/heads/master@{#328247}
|
|
|
|
|
|
|
|
| |
BUG=484142
Review URL: https://codereview.chromium.org/1126663002
Cr-Commit-Position: refs/heads/master@{#328242}
|
|
|
|
|
|
|
|
|
|
|
|
| |
R=tbreisacher@chromium.org
BUG=393873
NOTREECHECKS=true
NOTRY=true
Review URL: https://codereview.chromium.org/1118223003
Cr-Commit-Position: refs/heads/master@{#328228}
|