- 21 Jun, 2017 26 commits
-
-
pdfium-deps-roller@chromium.org authored
https://pdfium.googlesource.com/pdfium.git/+log/e10509a3d2a1..222e1a425e2d $ git log e10509a3d..222e1a425 --date=short --no-merges --format='%ad %ae %s' 2017-06-20 thestig Use early returns in more CPDFSDK_FormFillEnvironment code. 2017-06-20 npm Cleanup fpdf_parser_decode 2017-06-20 drgage Add FORM_GetSelectedText() function. 2017-06-20 thestig Add sample PDF with comboboxes. Created with: roll-dep src/third_party/pdfium BUG=59266 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, see: http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls TBR=dsinclair@chromium.org Change-Id: I2204c2ba8126e518115d094200db4b44c6042a8e Reviewed-on: https://chromium-review.googlesource.com/541859 Reviewed-by: <pdfium-deps-roller@chromium.org> Commit-Queue: <pdfium-deps-roller@chromium.org> Cr-Commit-Position: refs/heads/master@{#481061}
-
tedchoc authored
BUG=735145 Review-Url: https://codereview.chromium.org/2949903002 Cr-Commit-Position: refs/heads/master@{#481060}
-
szhangcs authored
BUG=734265 Review-Url: https://codereview.chromium.org/2711543002 Cr-Commit-Position: refs/heads/master@{#481059}
-
Luna Lu authored
Generated by script: grep -rli "lunalu" * | xargs -i@ sed -i 's/lunalu/loonybear/g' @ Change-Id: I022674b4e6dd8a30380539c38ff1dd949f92ade8 Reviewed-on: https://chromium-review.googlesource.com/533853Reviewed-by:
Pavel Feldman <pfeldman@chromium.org> Commit-Queue: Luna Lu <loonybear@chromium.org> Cr-Commit-Position: refs/heads/master@{#481058}
-
yosin authored
This is follow-up patch of the patch[1] which introduces |InSameLine()| to return wrong value for nodes without layout object. Original code: while (node && !node->GetLayoutObject() || InSameLine(...) The patch[1]: while (InSameLine(node, ...) InSameLine(Node* node) if (!node->GetLayoutObject()) return false; // This is wrong. This patch fixes this error. [1] http://crrev.com/2938923003: Introduce InSameLine() with Node and VisiblePosition BUG=734648 TEST=run_webkit_unit_tests --gtest_filter=VisibleUnitsTest.PreviousRootInlineBoxCandidatePositionWithDisplayNone Review-Url: https://codereview.chromium.org/2952563002 Cr-Commit-Position: refs/heads/master@{#481057}
-
yosin authored
This patch introduces |AdjustInlineBoxPositionForPrimaryDirection()| by moving code from then-clause of |AdjustInlineBoxPositionForTextNode()| with utilizing const-variable for improving readability. Note: The diff could be small but changing indentation makes diff larger. BUG=707656 TEST=n/a; no behavior changes Review-Url: https://codereview.chromium.org/2950763002 Cr-Commit-Position: refs/heads/master@{#481056}
-
Hiroshige Hayashizaki authored
ShouldAutoDetect(), DetectTextEncoding() and SetEncoding() calls and references to hint_* members are always coupled. This CL moves these code to AutoDetectEncodingIfAllowed() to make it clear that these are always coupled and executed only for |kUseAllAutoDetection|. Bug: 725654, 732893 Change-Id: Ia5a295bb2f600a4566f28738d421266ebb900343 Reviewed-on: https://chromium-review.googlesource.com/540179 Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#481055}
-
renjieliu authored
Apply switches as previosuly discussed so we easily turn off language detection logging or translation logging if something goes wrong. BUG=728491, 722679 Review-Url: https://codereview.chromium.org/2941953002 Cr-Commit-Position: refs/heads/master@{#481054}
-
Javier Fernandez authored
We applied too much abstraction to the logic to retrieve, or to compute if required, the grid item's margin so it was flow-aware. However, we don't need to apply such abstraction when accesing data that depends only on the grid item's writing mode. We are already applying a flow-aware logic to determine whether we need to use item's logical width or height; for example, we do this during the track sizing algorithm when computed content-sized tracks. There is no specific bug associated to this CL, this is just a refactoring. Hence, no specific additional tests are required. Change-Id: I0a50d1224588e71f99699be6d7fdbe55952a1db6 Reviewed-on: https://chromium-review.googlesource.com/540595 Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Reviewed-by:
Christian Biesinger <cbiesinger@chromium.org> Reviewed-by:
Sergio Villar <svillar@igalia.com> Cr-Commit-Position: refs/heads/master@{#481053}
-
Stephen Lanham authored
While my original CL strived to maintain conformity with Chrome, it turns out that Features names are not at all consistent. Switch to snake_case, which both supports our legacy features and is more comfortable for developers. This will avoid the inevitable error in the backend where a developer uses underscores and fails to activate their feature. BUG= b/35424335 Change-Id: Ie2da5666964720c7134e7375189ea84f1e34ea34 Reviewed-on: https://chromium-review.googlesource.com/542035 Commit-Queue: Stephen Lanham <slan@chromium.org> Reviewed-by:
Alok Priyadarshi <alokp@chromium.org> Cr-Commit-Position: refs/heads/master@{#481052}
-
patricialor authored
Update the icon and the string used for the infobar that shows up when changing the site settings via the Page Info bubble. See https://drive.google.com/open?id=0BzEa5HU1aAqBamtNSUlFNTBZM3M for before/after screenshots of the infobar. BUG=734831 TEST=Navigate to https://www.google.com/. Open the Page Info bubble by clicking the "Secure" lock, and change "Location" to "Block". Close the Page Info bubble and observe the infobar's new string and icon. Review-Url: https://codereview.chromium.org/2952543002 Cr-Commit-Position: refs/heads/master@{#481051}
-
Sam McNally authored
https://crrev.com/480682 left behind some includes no longer needed by mojo bindings to avoid updating clients that relied on those transitive includes in that CL. This removes those includes and updates those clients. TBR=piman@chromium.org,imcheng@chromium.org,emircan@chromium.org Bug: 678155 Change-Id: Id5ed5671bd58b8c91b3e7cb2edab827e819e1f5b Reviewed-on: https://chromium-review.googlesource.com/541116 Commit-Queue: Sam McNally <sammc@chromium.org> Reviewed-by:
Ken Rockot <rockot@chromium.org> Cr-Commit-Position: refs/heads/master@{#481050}
-
Tien-Ren Chen authored
When computing the conversion matrix between two spaces, there are two types of conversion that are commonly used, but with slightly different semantics: m1 = destination_to_screen ^ -1 * source_to_screen m2 = flatten(destination_to_screen) ^ -1 * flatten(source_to_screen) The former computes the space conversion, which is useful for mapping 3D points from one space to 3D points in another space. The latter computes the "projection through screen", which is useful for mapping 2D points from a plane to a backing that is expected to be drawn onto the screen. To illustrate the difference, see the following example: <div style="transform:rotateY(45deg)">A</div> <div style="transform:rotateY(-45deg)">B</div> The space conversion from A to B is equal to rotateY(90deg), but the projection between the two planes is identity. Prior to this CL, GeometryMapper implemented a mixed semantics. This is okay because all existing code only make queries that are co-planar, in which case, either version returns identical result. This is because we only make intra-compositing-layer queries, and 3D transform makes a compositing boundary. This CL changed the implementation to strictly return the "projection through screen". The algorithm runs in amortized O(1) by caching the matrix between a node and its nearest coplanar ancestor that has a invertible projection. Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: Ia526dc6feb60c902f27589d73e78dfea235c6a93 Reviewed-on: https://chromium-review.googlesource.com/534899 Commit-Queue: Tien-Ren Chen <trchen@chromium.org> Reviewed-by:
Chris harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#481049}
-
Matt Giuca authored
Previously, the method was visible, but calling it resulted in a SecurityError. Now it is simply gone (via [SecureContext] in the IDL). This brings the implementation in line with the draft spec at https://wicg.github.io/web-share. Bug: 734493 Change-Id: Ia246108fd7441f9b93bb0cbcf6a6fda4562d3a55 Reviewed-on: https://chromium-review.googlesource.com/541255 Commit-Queue: Matt Giuca <mgiuca@chromium.org> Reviewed-by:
Sam McNally <sammc@chromium.org> Cr-Commit-Position: refs/heads/master@{#481048}
-
thanhph authored
dependency will be removed and replaced by ViewTestBase. Appropriate UIElement trees are also created to test DevTools. BUG=701835 Review-Url: https://codereview.chromium.org/2899783002 Cr-Commit-Position: refs/heads/master@{#481047}
-
megjablon authored
The Previews infobar should read "Simplified page to save data and load faster. Options available near bottom of the screen." when shown, rather than reading the infobar strings. BUG=732944 Review-Url: https://codereview.chromium.org/2939143002 Cr-Commit-Position: refs/heads/master@{#481046}
-
chenwilliam authored
Improvements: * devtools drives the test, not the inspected page * tests are pure JS * doc-typed test harness * improved debugging experience (surround test function with TestRunner.debugTest) This copies a couple of existing tests - once this infra has been proven, we'll delete the originals. Perf: - Old (66 sec) [0] - New (45 sec) [1] [0] src/blink/tools/run_layout_tests.py --repeat-each=100 inspector/console/console-clear.html [1] src/blink/tools/run_layout_tests.py --repeat-each=100 http/tests/inspector/devtools-js/console-clear.js BUG=667560 Review-Url: https://codereview.chromium.org/2837083003 Cr-Commit-Position: refs/heads/master@{#481045}
-
allada authored
This patch fully removes the dependency from NetworkRequest to NetworkManager. R=dgozman,pfeldman BUG=374557 Review-Url: https://codereview.chromium.org/2921963002 Cr-Commit-Position: refs/heads/master@{#481044}
-
rdsmith authored
BUG=723734 R=mmenke@chromium.org Review-Url: https://codereview.chromium.org/2909533002 Cr-Commit-Position: refs/heads/master@{#481043}
-
oshima authored
* Remove unsupported 1.5x. * Removed obsolete use_125_dsf_for_ui_scaling flag. (it should be always true) * Added large FHD screen scenario. BUG=734204 BUG=b/62475614 TEST=Updated unit tests. Manual test on cave with manually teaking the scale. Review-Url: https://codereview.chromium.org/2945913003 Cr-Commit-Position: refs/heads/master@{#481042}
-
Chris Mumford authored
Converted a LOG_IF to a DLOG_IF to eliminate spam. BUG=735249 Change-Id: Ic2642d5dc860ad6a43c2a54d1548018611024c84 Reviewed-on: https://chromium-review.googlesource.com/541899Reviewed-by:
Joshua Bell <jsbell@chromium.org> Commit-Queue: Joshua Bell <jsbell@chromium.org> Commit-Queue: Chris Mumford <cmumford@chromium.org> Cr-Commit-Position: refs/heads/master@{#481041}
-
James Zern authored
these are currently intended to be built using the host toolchain and used on the host rather than the target; modeled after imagediff. BUG=695482,732565 Change-Id: I3d95d9526ecef3026bbbaf4a13525cf6add02062 Reviewed-on: https://chromium-review.googlesource.com/540703Reviewed-by:
Urvang Joshi <urvang@chromium.org> Commit-Queue: James Zern <jzern@google.com> Cr-Commit-Position: refs/heads/master@{#481040}
-
Morten Stenshorne authored
In LayoutGeometryMap, when there's a non-uniform step (e.g. when inside multicol), we fall back on doing it the slow way, i.e. we involve LayoutObject::MapLocalToAncestor(). The mode flags initially passed from ClientQuads() will just be echoed here, so we need to make sure that kUseTransforms is specified. BUG=683925 Change-Id: I2a6fe83fb1332a19a581203d6c44c6924da3f027 Reviewed-on: https://chromium-review.googlesource.com/541339Reviewed-by:
Chris harrelson <chrishtr@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@opera.com> Cr-Commit-Position: refs/heads/master@{#481039}
-
Kevin Gibbons authored
Also add self to AUTHORS. Bug: v8:6504 Change-Id: Ia5bceee91c7589bc53198e69c5623f1a26918c02 Reviewed-on: https://chromium-review.googlesource.com/541718 Commit-Queue: Adam Klein <adamk@chromium.org> Reviewed-by:
Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#481038}
-
jiameng authored
This cl contains the following changes * API impl of the three shorthand properties (CSSShorthandPropertyAPIOverflow, CSSShorthandPropertyAPIFont, CSSShorthandPropertyAPIFontVariant). * Moved ConsumeFontVariantCSS21 from CSSPropertyParser.cpp to CSSPropertyFontUtils. - this function is being used by CSSShorthandPropertyAPIFont and also another function from CSSPropertyParser.cpp. * Changed CSSPropertyParser.cpp to use the new API parseShorthand for the three properties above. Additional changes are: - moved two helper functions (ConsumeSystemFont and ConsumeFont) to be private functions of CSSShorthandPropertyAPIFont. - removed ConsumeFontVariantShorthand that's no longer needed. * Added the properties API to BUILD file and CSSProperties.json5. * Changed AddProperty signature so that "implicit" is now an enum. - We previously passed on bool literals to this function. This change makes the function follow the style guide. Diff: https://gist.github.com/810c7e46324ff8db8efb6f34ddfdad42/revisions Review-Url: https://codereview.chromium.org/2938983002 Cr-Commit-Position: refs/heads/master@{#481037}
-
Donna Wu authored
This CL replaces ScopedVector with std::vector<std::unique_ptr> in components/cronet. ScopedVector is deprecated, see bug. BUG=554289 Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester Change-Id: I93ed1cac20093344cc9d46c648f02cb579629794 Reviewed-on: https://chromium-review.googlesource.com/536240 Commit-Queue: Han Leon <leon.han@intel.com> Reviewed-by:
Helen Li <xunjieli@chromium.org> Cr-Commit-Position: refs/heads/master@{#481036}
-
- 20 Jun, 2017 14 commits
-
-
afakhry authored
Demo: https://bugs.chromium.org/p/chromium/issues/detail?id=705816#c20 BUG=705816 Review-Url: https://codereview.chromium.org/2950673002 Cr-Commit-Position: refs/heads/master@{#481035}
-
mark a. foltz authored
TBR=wez Bug: Change-Id: I3016dea4130a0020158cb5d0ff610b6c4fa19268 Reviewed-on: https://chromium-review.googlesource.com/541897Reviewed-by:
mark a. foltz <mfoltz@chromium.org> Commit-Queue: mark a. foltz <mfoltz@chromium.org> Cr-Commit-Position: refs/heads/master@{#481034}
-
Florin Malita authored
We currently build Skia with SK_IGNORE_GPU_DITHER, effectively disabling GPU dithering. Remove the build flag to align Ganesh with the sw rasterizer dithering behavior. Note: Blink only sets the SkPaint dither flag for gradients at this time. Aside from the flag change, this CL includes: * a handful of trivial layout tests rebaselines * some Canvas layout/unit test adjustments (relaxed exact pixel value checks to accommodate dithering) * a couple of trivial GPU pixel test rebaselines BUG=731693 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: I2fc6f8d23272504838c55427c48c4ea7d641deae Reviewed-on: https://chromium-review.googlesource.com/535714Reviewed-by:
Kenneth Russell <kbr@chromium.org> Reviewed-by:
Mike Reed <reed@chromium.org> Commit-Queue: Florin Malita <fmalita@chromium.org> Cr-Commit-Position: refs/heads/master@{#481033}
-
updowndota authored
- Add a new OOBE screen for waiting for container ready. - The screen will be shown after user click Continue in the value prop screen. - The screen will show a progress animation while container is initializing. - The OOBE flow will end after container is ready or a one minute timeout is reached. - A temporary 5 second delay is added to avoid potential racing issue. BUG=b/62549680 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Review-Url: https://codereview.chromium.org/2947483002 Cr-Commit-Position: refs/heads/master@{#481032}
-
braveyao authored
It's required recently that any extension loaded from a directory as an unpacked extension in chrome://extensions must be whitelisted with a unique whitelisted ID. Otherwise it will be blocked from being installed. Bug: 735242 Change-Id: I7c5aa5460cee5f17e76ef7fc4473ed9cf48e0bea Reviewed-on: https://chromium-review.googlesource.com/541955Reviewed-by:
Ken Rockot <rockot@chromium.org> Commit-Queue: Weiyong Yao <braveyao@chromium.org> Cr-Commit-Position: refs/heads/master@{#481031}
-
Anton Vayvod authored
Using the ScreenAvailability enum added in https://chromium-review.googlesource.com/c/527376/ in content/browser and chrome/browser/ BUG=723032 TEST=existing/updated tests Change-Id: I6667f4d6237c242dfe9446cbf9e82dd30f0858ec Reviewed-on: https://chromium-review.googlesource.com/530284 Commit-Queue: Anton Vayvod <avayvod@chromium.org> Reviewed-by:
mark a. foltz <mfoltz@chromium.org> Reviewed-by:
Derek Cheng <imcheng@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#481030}
-
pdr authored
Revert of Move SafeBrowsing files from //chrome/browser to a separate target. (patchset #5 id:80001 of https://codereview.chromium.org/2940403002/ ) Reason for revert: This caused compile failures (https://uberchromegw.corp.google.com/i/chromium.win/builders/Win%20x64%20Builder/builds/34160) Original issue's description: > Move SafeBrowsing files from //chrome/browser to a separate target. > > BUG= > > Review-Url: https://codereview.chromium.org/2940403002 > Cr-Commit-Position: refs/heads/master@{#481019} > Committed: https://chromium.googlesource.com/chromium/src/+/e4da0e76b5b75d453fec094f62ad06659e66708e TBR=rockot@chromium.org,vakh@chromium.org,yzshen@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG= Review-Url: https://codereview.chromium.org/2951883002 Cr-Commit-Position: refs/heads/master@{#481029}
-
Sam McNally authored
Bug: 654988 Change-Id: I7f91eafc52aed40c8243e657b85c821605f9c76b Reviewed-on: https://chromium-review.googlesource.com/526914Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Commit-Queue: Sam McNally <sammc@chromium.org> Cr-Commit-Position: refs/heads/master@{#481028}
-
oshima authored
This can happen when rotation animator sets the orientation after animation is completed. We shouldn't save this anyway, as we changed the semantics as follows: a) A user/API driven rotation change in tablet mode should be treated as user locked rotation. b) A user will not be able to change the orientation in tablet mode from settings. BUG=734107 TEST=Manual + unit test Review-Url: https://codereview.chromium.org/2951773002 Cr-Commit-Position: refs/heads/master@{#481027}
-
lukasza authored
This CL addresses a TODO from chrome/renderer/chrome_render_view_observer.cc to associate ChromeViewMsg_GetWebApplicationInfo and ChromeViewHostMsg_DidGetWebApplicationInfo IPCs with frame, rather than view. This CL helps ensure that ChromeRenderFrameObserver::OnGetWebApplicationInfo (formerly a method of ChromeRender*View*Observer) always operates on a local frame (and therefore this CL helps with moving GetDocument method from WebFrame to WebLocalFrame in a follow-up CL - https://crrev.com/2928033002). BUG=416660 Review-Url: https://codereview.chromium.org/2942583004 Cr-Commit-Position: refs/heads/master@{#481026}
-
Mounir Lamouri authored
Different types are: inline, fullscreen and picture-in-picture. Bug: 727322 Change-Id: I72bfa1a1f8f46079880f60cfd5b5d886875d06d6 Reviewed-on: https://chromium-review.googlesource.com/528082Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
Philip Jägenstedt <foolip@chromium.org> Reviewed-by:
Dale Curtis <dalecurtis@chromium.org> Commit-Queue: Mounir Lamouri <mlamouri@chromium.org> Cr-Commit-Position: refs/heads/master@{#481025}
-
Yuzhu Shen authored
BUG=None Change-Id: I4f0c8fd5a24a5bfc1f3a81c96026a33c7700639e Reviewed-on: https://chromium-review.googlesource.com/538980 Commit-Queue: Yuzhu Shen <yzshen@chromium.org> Reviewed-by:
Randy Smith <rdsmith@chromium.org> Cr-Commit-Position: refs/heads/master@{#481024}
-
Wez authored
The patch which added the butter-bar for unimplemented modes broke the task-profiler case for the heap-profiling flag. Bug: 705461 Change-Id: Ib293ce8aa8d4c2f763c7b9ba414923381f2d9870 Reviewed-on: https://chromium-review.googlesource.com/540983Reviewed-by:
Sigurður Ásgeirsson <siggi@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#481023}
-
estark authored
This CL sends the Expect-CT expiration into the reporter, to include in the report as key "effective-expiration-date". http://httpwg.org/http-extensions/expect-ct.html#rfc.section.3.1 BUG=679012 Review-Url: https://codereview.chromium.org/2944953002 Cr-Commit-Position: refs/heads/master@{#481022}
-