GitLab

This patch changes SVGInlineTextMetricsIterator to keep an instanace of
LineLayoutSVGInlineText, not a pointer to. LineLayoutItem and its
subclasses are oftentimes allocated on stack that keeping pointers
should be avoided.

Additional ASSERTs in this CL fail existing tests. These existing tests
cover the fix.

BUG=572399, 499321

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

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

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/56ce1b39..b238476a

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

TBR=hablich@chromium.org,machenbach@chromium.org,yangguo@chromium.org,vogelheim@chromium.org

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

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

Almost all consumers use already scoped_ptr
and one place is much simpler when changed to use scoped_ptr.

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

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

The correct capability for v4l2 devices should be V4L2_CAP_VIDEO_M2M_MPLANE.
V4L2_CAP_VIDEO_CAPTURE_MPLANE and V4L2_CAP_VIDEO_OUTPUT_MPLANE will be
deprecated. Nyan doesn't report V4L2_CAP_VIDEO_M2M_MPLANE yet. So check
both capabilities in V4L2VDA and V4L2VEA.

BUG=chromium:572132
TEST=Run tests on nyan, peach, and veyron.

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

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

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

https://chromium.googlesource.com/skia.git/+log/636270245fb4..8895b72f789e

$ git log 636270245..8895b72f7 --date=short --no-merges --format='%ad %ae %s'
2015-12-28 mtklein Try using std::call_once

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

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

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

Linux desktop gcc build is failing with below error:
In file included from ../../chrome/browser/ui/webui/interstitials/interstitial_ui.cc:12:0:
../../chrome/browser/safe_browsing/safe_browsing_blocking_page.h:143:16:
error: ‘safe_browsing::SafeBrowsingBlockingPageTest_MalwareReportsToggling_Test’
is already a friend of ‘safe_browsing::SafeBrowsingBlockingPage’ [-Werror]
   FRIEND_TEST_ALL_PREFIXES(SafeBrowsingBlockingPageTest,

../../chrome/browser/safe_browsing/safe_browsing_blocking_page.h:143:87:
error: ‘safe_browsing::SafeBrowsingBlockingPageTest_DISABLED_MalwareReportsToggling_Test’
is already a friend of ‘safe_browsing::SafeBrowsingBlockingPage’ [-Werror]
   FRIEND_TEST_ALL_PREFIXES(SafeBrowsingBlockingPageTest,

../../chrome/browser/safe_browsing/safe_browsing_blocking_page.h:143:167:
error: ‘safe_browsing::SafeBrowsingBlockingPageTest_FLAKY_MalwareReportsToggling_Test’
is already a friend of ‘safe_browsing::SafeBrowsingBlockingPage’ [-Werror]
   FRIEND_TEST_ALL_PREFIXES(SafeBrowsingBlockingPageTest,

Android build had no issues.

BUG=NONE
TESTS=NONE

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

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

The resource strings are needed only for the setup app and unit tests. Previously they were also linked into Chrome.

This clarifies the usage and renames the targets to force you to pick (previously the naming encouraged you to link to the strings, which is probably not correct for most cases.

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

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

Use scoped_ptr in Files because then we can make it simpler and
everything get always deleted. Also
removed unused clone function.

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

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

blink::Animation can loose compositorPlayer if Animation::m_content detached via
Animation::setEffect(nullptr)

If KeyframeEffect::cancelAnimationOnCompositor wants to clear m_compositorAnimationIds
then it shouldn't crash.

Also, note the existing comment in CompositorAnimations::cancelAnimationOnCompositor (above changed lines)

BUG=571504
R=dstockwell@chromium.org

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

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

BUG=554269

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

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

This change fixed the bug in framebuffer-object-attachment.html

BUG=295792
TEST=conformance2/renderbuffers/framebuffer-object-attachment.html

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

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

Continue the refactoring from https://codereview.chromium.org/1504083002
by moving most of the detail in this function to helper functions. This
makes the behaviour of the function more explicit - namely a loop that
skips over non-whitespace and/or collapsible whitespace but returns early
if it encounters a soft or hard line-breaking opportunity.

BUG=567080

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

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

This is a partial revert of:
https://codereview.chromium.org/1449953002

Most of that CL is inactive code, but it did change the way the
compositor thread was created. Instead of a base::Thread, I'd used a
WebThreadImplForWorkerScheduler and this seems to have had some
performance impact. While I try to figure out why, this CL should get
us back to our prior performance.

BUG=565789

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

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

(╯^□^)╯︵ ❄☃❄

BUG=557422
R=avi@chromium.org
TBR=jam@chromium.org

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

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

This reverts commit 83557154.

BUG=553569

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

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

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

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

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

Previously, if a linearized PDF was loaded in a single callback (i.e. if
IsDocumentComplete was true in the call to LoadDocument), only the first
page of the document was visible because FPDFAvail_IsPageAvail was never
called for all other pages. This has been corrected.

BUG=572655

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

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

After John's work in crbug.com/560559, telemetry project no longer depends
on pylib, hence tools/perf which is a user of telemetry must specify this
deps explictly.

BUG=572700, 560559
TBR=jbudorick@chromium.org

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

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

(╯^□^)╯︵ ❄☃❄

BUG=557422
R=avi@chromium.org
TBR=lcwu@chromium.org

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

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

std::move is not needed when returning local variables. This wasn't
caught in the initial commit because only Windows builds //third_party
with -Wall.

BUG=82385
TBR=thakis@chromium.org

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

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

BUG=561190

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

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

We currently resolve nearby URLs twice, once before showing a "nearby web
pages found" notification and once just before displaying the list of
nearby URLs. If a URL was not resolvable for the notification we avoid
re-resolving it for display. This prevents costly delays at display time
as we are only requesting data expected to already be cached by the
resolution service.

During onboarding (ie, before the user has explicitly opted into the
physical web feature) we still scan for nearby URLs but do not resolve
them for privacy reasons. This causes all URLs to be considered
"unresolvable" immediately after opting in as none have been sent to the
resolution service yet.

To fix, at display time allow ListUrlsActivity to receive the full
list of nearby URLs (including unresolved) only if the resolved list is
empty.

BUG=529962

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

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

Exactly the same as issue 1528243002 at patchset 20001 (http://crrev.com/1528243002#ps20001)

BUG=534894

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

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

BUG=571302,510410,532249

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

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

The current blacklist entry will exclude any Optimus configuration when
GPU driver that isn't "Mesa >= 10.1".  This is (unintentionally) blocking
GPU on devices where the NVIDIA driver is used.

This CL changes the intent so that we blacklist "Mesa < 10.1" rather than
"anything except Mesa >= 10.1".

BUG=530981

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

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

BUG=532905

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

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

Instead of allocating and mapping a new chunk of shared memory segment
in each draw synchronously, re-use the same segment if the sizes match
exactly.

Break software draws into 3 IPCs:
SetSharedMemory: synchronous, pass the shared memory handle to be used
                 for subsequent software draws to renderer
DemandDrawSw: synchronous, the draw itself
ZeroSharedMemory: asynchronous, zeros shared memory on renderer side,
                  sent after each DemandDrawSw after browser is done
                  reading from the shared memory.

ZeroSharedMemory is asynchronous so zero-ing the memory can be done in
parallel. Note messages on renderer are ordered, so ZeroSharedMemory
is guaranteed to be handled before the next DemandDrawSw.

BUG=545611

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

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

BUG=532905

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

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

The main GraphicsLayer of a composited scroller should be the size of the
scroller's frame.  Report this size in PaintLayer::boundingBoxForCompositing
and update ViewPainter to use the same rect when painting the background fill.

This fixes placement of scrollbar layers in RTL documents, which were confused
by a bogus m_offsetFromLayoutObject because the rect returned by
LayoutView::documentRect is relative to the scroll origin.

This patch makes compositing/rtl/rtl-overflow-invalidation.html pass (discovered
through flag-specific expectations!)

Sadly we regress several repaint-tracking tests due to the new invalidation in
FrameView::viewportSizeChanged.  These will need flag-specific baselines (not
yet implemented) at least until http://crbug.com/568847 is addressed.

BUG=542432

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

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

Diff since last roll:
https://github.com/chromium/dom-distiller/compare/6e47a6727c...349b932fc2

Picked up changes:
349b932 Remove DOM Distiller dependency on scoped_ptr<T>::Pass().
8fa737b Add <pre> to nesting tags
7991208 Clean up attributes of image elements

BUG=557422,567955
TBR=mdjones@chromium.org

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

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

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

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

If the dialog is initially in route-details view, and the route is
closed before the 3s startup timer fires, then the dialog will flash
between the route-details and sink-list view before settling on
sink-list. See bug for details.

The fix is to only allow maybeShowRouteDetailsOnOpen to be invoked
once, on startup. It is removed from |rebuildRouteMaps_| and is now
called from setInitialData. Also removed |localRouteCount_| field from
media-router-container since it's no longer needed.

BUG=571463

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

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

BUG=568353

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

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

Apparently cmake doesn't like it if the compiler changes like it did in
https://codereview.chromium.org/1555443002/ without a clobber build.

Since this might help with issue 569337 too (who knows), do it everywhere
for a short while instead of just on linux.

BUG=509739,569337
TBR=hans

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

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

If we do not already have the location permission, we need to request
it when the user enables the Physical Web feature in the privacy
settings.

BUG=529962

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

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

Display a dialog describing the Physical Web and inviting the user to
enable or decline the feature.

BUG=529962

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

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

That way, the libstdc++ that's used by default should work on the bots.
Before this change, one had to pass --gcc-toolchain pointing to a precise-built
gcc when building linux clang binaries.

BUG=509739
TBR=hans@chromium.org

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

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

BUG=529962

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

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