| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
|
| |
|
|
|
|
|
| |
Cr-Commit-Position: refs/branch-heads/2623@{#644}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
| |
Cr-Commit-Position: refs/branch-heads/2623@{#643}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
| |
Cr-Commit-Position: refs/branch-heads/2623@{#642}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
| |
Cr-Commit-Position: refs/branch-heads/2623@{#641}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
| |
Cr-Commit-Position: refs/branch-heads/2623@{#640}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
DTL::reportResponseReceived()
BUG=578849
Review URL: https://codereview.chromium.org/1603783002
(cherry picked from commit d2535dca624b5531247dbcbc2048dded6e9c45fc)
Cr-Original-Commit-Position: refs/heads/master@{#370674}
Cr-Commit-Position: refs/branch-heads/2623@{#639}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch ensures that we process active low res pending high res
tilings, since they can have required for activation tiles. Previously,
this only applied to non ideal tiles, but clearly it's possible to hit
the rare case of low res on active while high res on pending.
R=enne, chrishtr
BUG=595209
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
Review URL: https://codereview.chromium.org/1808043002
(cherry picked from commit ad3070d0f8f9b7513222014d218d0937da6d8077)
Cr-Original-Commit-Position: refs/heads/master@{#381613}
Cr-Commit-Position: refs/branch-heads/2623@{#638}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update.
This fixes the referenced bug, as well as cleaning up the interaction between
PictureLayer and DisplayListRecordingSource a little bit. This way both the
invalidation and picture come from DisplayListRecordingSource, rather than one
coming from PictureLayer and the other from DisplayListRecordingSource, with the
latter modifying the invalidation during Update.
Also renamed LayerImpl::GetInvalidationRegion() to
LayerImpl::GetInvalidationRegionForDebugging() to make clear it's only used for
that purpose.
BUG=591561
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
Review URL: https://codereview.chromium.org/1812733003
Cr-Commit-Position: refs/heads/master@{#381977}
(cherry picked from commit c41aca7b408e13fdee88a3b39db1a93813bd9fc1)
Review URL: https://codereview.chromium.org/1811113004 .
Cr-Commit-Position: refs/branch-heads/2623@{#637}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
TEST=RepostFormWarningTest#testFormResubmissionTabDestroyed
BUG=580284
Review URL: https://codereview.chromium.org/1731703002
Cr-Commit-Position: refs/heads/master@{#377450}
Review URL: https://codereview.chromium.org/1815323003 .
Cr-Commit-Position: refs/branch-heads/2623@{#636}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Autofill code ignores non-user-gesture-based form updates since they are often
greyed-out filler text or suggestions. KeyDown events as well as
IME setComposition were already correctly registered as user gestures, but
commitText was not. This could cause autofill to save partially typed form
fields.
BUG=582401
Review URL: https://codereview.chromium.org/1644993002
(cherry picked from commit 6ad2101efa6830ca3f9d156d662b977707b8ceff)
Cr-Original-Commit-Position: refs/heads/master@{#374340}
Cr-Commit-Position: refs/branch-heads/2623@{#635}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Left upper corner of the rect may not always be the starting position
in the DOM hierarchy, and this assumption was causing crashes.
BUG=589082
Review URL: https://codereview.chromium.org/1806813004
(cherry picked from commit cddc46848415206666281dfb0cefbb8eba1f7aed)
Cr-Original-Commit-Position: refs/heads/master@{#381838}
Cr-Commit-Position: refs/branch-heads/2623@{#634}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a follow up fix to r361481. After r361481 additional info
about a LoadDataWithBaseURL is stored in DocumentState.
However, if there is an in-page fragment navigation, this additional
info is just thrown away, causing incorrect behavior. Fix this by not
updating this additional info for in-page navigations.
Note this is NOT a fix for crbug.com/561034, which describes a similar
problem, but on the browser side.
BUG=594611
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation
Review URL: https://codereview.chromium.org/1802383004
Cr-Commit-Position: refs/heads/master@{#381588}
(cherry picked from commit ac512fd1188a7bd1e1e752bd46990acd72b6bdb6)
Review URL: https://codereview.chromium.org/1813353002 .
Cr-Commit-Position: refs/branch-heads/2623@{#633}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch removes LayoutSVGText::subtreeStyleDidChange which was
added in [1] to fix a font face crash. We no longer support SVG fonts
and subtreeStyleDidChange should never have been called on every layout
in the first place.
With this patch we mark LayoutSVGText as needing a text metrics update
when a child inline's style changes, and recalculate the text metrics
during layout.
This patch results in a 45% improvement on the SVGCubics benchmark
which is the heaviest SVG text benchmark we have.
[1] https://src.chromium.org/viewvc/blink?revision=167993&view=revision
BUG=589525
Review URL: https://codereview.chromium.org/1770663002
Cr-Commit-Position: refs/heads/master@{#379566}
(cherry picked from commit d0ffb54118db1b76565dd6d3ffe7623227663038)
Review URL: https://codereview.chromium.org/1809203004 .
Cr-Commit-Position: refs/branch-heads/2623@{#632}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GraphicsLayer::paint may not be a no-op if there happened to be dirty layout or
paint since the last time a synchronized paint occurred.
BUG=585694
TBR=ajuma@chromium.org
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
Review URL: https://codereview.chromium.org/1690763003
Cr-Commit-Position: refs/heads/master@{#374864}
(cherry picked from commit 4d0892b08c7f42a433a278c05498d7c6ddbe8eeb)
Review URL: https://codereview.chromium.org/1812093002 .
Cr-Commit-Position: refs/branch-heads/2623@{#631}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
| |
Cr-Commit-Position: refs/branch-heads/2623@{#630}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=590284
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation
Review URL: https://codereview.chromium.org/1738233002
Cr-Commit-Position: refs/heads/master@{#378461}
(cherry picked from commit 8be1ff11dc1fae61146dbcfaa38e12314d290dca)
Review URL: https://codereview.chromium.org/1811783002 .
Cr-Commit-Position: refs/branch-heads/2623@{#629}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=582263
Review URL: https://codereview.chromium.org/1805103002
Cr-Commit-Position: refs/heads/master@{#381325}
(cherry picked from commit 5d6de5d3bba98d3345fee4036e4439c87fc7e868)
Review URL: https://codereview.chromium.org/1812643002 .
Cr-Commit-Position: refs/branch-heads/2623@{#628}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As it turns out that the committed entry may omit the base
URL if there has been a javascript: URL navigation after
LoadDataWithBaseURL. Thus we have to store the base url on
DidStartLoading and use it in DidStopLoading / DidFinishLoad.
We have to preserve the old hack with SetToBaseURLForDataURLIfNeeded
because if the base URL is not valid, DidFinishLoad doesn't
receive it from the renderer.
This change is a short-term workaround. The correct solution
is to pass a flag that the load was through LoadDataWithBaseURL
via Blink, so base URL can be restored correctly within
NavigationController.
BUG=594001
Review URL: https://codereview.chromium.org/1779363004
Cr-Commit-Position: refs/heads/master@{#381108}
(cherry picked from commit ce1f4d009316d8f5f4c49b18e1bd94687d80c59d)
Review URL: https://codereview.chromium.org/1806853005 .
Cr-Commit-Position: refs/branch-heads/2623@{#627}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To be merged to 49 to inform users that updates are over.
R=sky@chromium.org
BUG=582262
Review URL: https://codereview.chromium.org/1799373002
Cr-Commit-Position: refs/heads/master@{#381238}
(cherry picked from commit 7a1f43f10cf484c74382383f3827e74462fb4e2d)
Review URL: https://codereview.chromium.org/1806993002 .
Cr-Commit-Position: refs/branch-heads/2623@{#626}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will force old configs to add this setting on the next update, and
thus get rid of the "missing i386" warning for existing users.
R=phajdan.jr@chromium.org, thestig@chromium.org
BUG=591480
Review URL: https://codereview.chromium.org/1801283002
Cr-Commit-Position: refs/heads/master@{#381287}
(cherry picked from commit 8b58c0d445772371cba4da0000f78917a12c79bc)
Review URL: https://codereview.chromium.org/1800323002 .
Cr-Commit-Position: refs/branch-heads/2623@{#625}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We were doing this in gyp builds but not GN; add this in the GN config
too so that we can be sure crash symbols match.
BUG=594975
R=agrieve@chromium.org
Review URL: https://codereview.chromium.org/1801073002 .
Cr-Commit-Position: refs/heads/master@{#381242}
(cherry picked from commit e67cbae553e592e7683aefc74c775f1e4a99296a)
Review URL: https://codereview.chromium.org/1801243002 .
Cr-Commit-Position: refs/branch-heads/2623@{#624}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Checking VerQueryValue() of kernel32 reports the "real" OS, rather than
the potentially shimmed one that GetVersionEx() reports.
Normally it's better to use GetVersionEx() because that'll determine the
APIs that are available and how they behave. However, we'd like to know
if there are a substantial percentage of users in compatibility mode, as
there have been complaints of users seeing the "XP and Vista are no
longer supported" infobar on Windows 7.
R=asvitkine@chromium.org, robliao@chromium.org, wfh@chromium.org, nick@chromium.org
BUG=581499
Review URL: https://codereview.chromium.org/1784623003
Cr-Commit-Position: refs/heads/master@{#380793}
(cherry picked from commit d68b1e1c89ab3d8055046883b1bf726084673959)
Review URL: https://codereview.chromium.org/1799423002 .
Cr-Commit-Position: refs/branch-heads/2623@{#623}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=582968
Review URL: https://codereview.chromium.org/1700513002
Cr-Commit-Position: refs/heads/master@{#377667}
(cherry picked from commit d73b3bb2e4600c44695fd27fadf7934a14c63418)
Review URL: https://codereview.chromium.org/1804873002 .
Cr-Commit-Position: refs/branch-heads/2623@{#622}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
| |
Cr-Commit-Position: refs/branch-heads/2623@{#621}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=566588
Review URL: https://codereview.chromium.org/1779323002
Cr-Commit-Position: refs/heads/master@{#380524}
(cherry picked from commit e555844403d02ae83b70d4c6be174bd1ee09716b)
Review URL: https://codereview.chromium.org/1800783002 .
Cr-Commit-Position: refs/branch-heads/2623@{#620}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Tab switching can cause canvases to go blank on Mac.
This is a temporary solution until a proper fix can be found.
BUG=588434
Review URL: https://codereview.chromium.org/1762783002
Cr-Commit-Position: refs/heads/master@{#380245}
(cherry picked from commit db1d1c9054628f3c0b2e46029447aa08635b13d0)
Review URL: https://codereview.chromium.org/1801713002 .
Cr-Commit-Position: refs/branch-heads/2623@{#619}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
| |
Cr-Commit-Position: refs/branch-heads/2623@{#618}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
| |
Cr-Commit-Position: refs/branch-heads/2623@{#617}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
| |
Cr-Commit-Position: refs/branch-heads/2623@{#616}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
| |
Cr-Commit-Position: refs/branch-heads/2623@{#615}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The experiment has been 100% enabled for several months now. With this
change, the delay agnostic AEC is always enabled (for desktops) unless
switches::kDisableDelayAgnosticAec disables it.
BUG=450193
Review URL: https://codereview.chromium.org/1603693004
Cr-Commit-Position: refs/heads/master@{#370370}
(cherry picked from commit 2622d7364c69af1f6cc53e5f53a0d8f7eb116aaf)
Review URL: https://codereview.chromium.org/1792513002 .
Cr-Commit-Position: refs/branch-heads/2623@{#614}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Crashpad will only create one level of directory for its database
storage. On Windows, the target is %LOCALAPPDATA%\Google\Chrome\User
Data\Crashpad.
However, on first run when Crashpad is initialized, "User Data" will not
yet have been created. We don't want to move Crashpad initialization
later in startup, so we instead create the directory if it does not
exist.
Note that this is calling file_util::CreateDirectory(), rather than
CreateDirectoryW() which means the full parent tree will be created, not
just the last entry in the path.
R=thakis@chromium.org,wfh@chromium.org
TEST=remove local user data dir, install chrome, confirm that chrome --process-type=crashpad-handler exists on first run
BUG=591504
Review URL: https://codereview.chromium.org/1774573002
Cr-Commit-Position: refs/heads/master@{#379676}
(cherry picked from commit 92905ef36a30be9be9041d8ee07ccd6e7ca45d64)
Review URL: https://codereview.chromium.org/1790493003 .
Cr-Commit-Position: refs/branch-heads/2623@{#613}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
| |
Cr-Commit-Position: refs/branch-heads/2623@{#612}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
JS setters invalidate the pointers frame, data_source and document_state.
BUG=590455
Review URL: https://codereview.chromium.org/1751553002
Cr-Commit-Position: refs/heads/master@{#379047}
(cherry picked from commit 9d92ff158726601ae5c044d62050614f076eaae4)
Review URL: https://codereview.chromium.org/1782323002 .
Cr-Commit-Position: refs/branch-heads/2623@{#611}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
| |
BUG=593186
TBR=szager
Review URL: https://codereview.chromium.org/1782963003 .
Cr-Commit-Position: refs/branch-heads/2623@{#610}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Blink and cc have different notions of scroll offset - Blink's is relative to
the scroll origin which is non-zero in RTL documents.
The CompositorScrollOffsetAnimationCurve must work entirely in cc scroll offsets
since it is handed over to cc which doesn't know about the scroll origin.
This patch teaches ScrollAnimator and ProgrammaticScrollAnimator to convert in
both directions when creating and using the curve object.
BUG=581264
Review URL: https://codereview.chromium.org/1776503002
Cr-Commit-Position: refs/heads/master@{#379974}
(cherry picked from commit 0bb16600006793953292ee1e7fd8bf0a66f575dc)
Review URL: https://codereview.chromium.org/1777353002 .
Cr-Commit-Position: refs/branch-heads/2623@{#609}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
| |
Cr-Commit-Position: refs/branch-heads/2623@{#608}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
| |
Cr-Commit-Position: refs/branch-heads/2623@{#607}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
| |
Cr-Commit-Position: refs/branch-heads/2623@{#606}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In RenderWidgetHostViewGuest::OnSwapCompositorFrame() we currently
detect if the guest has been detached, and if it has we clear the
compositor surface and exit without processing the frame we've been
given.
Based on the repro app in the associated bug, it seems that if this
happens, it prevents subsequent frames from being sent, presumably
on account of the most recent frame remaining unsatisfied.
This CL modifies the logic to complete processing of the frame, and
then clearing the surface. This appears to prevent the behaviour
observed in the bug.
BUG=581440
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation
Review URL: https://codereview.chromium.org/1772393002
Cr-Commit-Position: refs/heads/master@{#380134}
(cherry picked from commit 17f1c1ded552cbcd11cac1b7985593ea2c847808)
Review URL: https://codereview.chromium.org/1776673005 .
Cr-Commit-Position: refs/branch-heads/2623@{#605}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
immersive fullscreen.
This regressed in r362878 which didn't handle a case where animations
occur in immersive fullscreen.
To fix, disable layer-painting of tab spinners while in fullscreen.
In most cases the tab is hidden or animating; layers shouldn't
be used. When the tab strip is fully revealed we could use layers,
but the benefit isn't worth the extra logic.
TBR=tapted@chromium.org
BUG=591535
TEST=On CrOS, enter immersive fullscreen, reload a page, reveal the
tab strip while the page is still loading, then move the mouse down
to dismiss the tab strip. Ensure a frozen throbber doesn't stick
around, floating over the page.
Review URL: https://codereview.chromium.org/1758183002
Cr-Commit-Position: refs/heads/master@{#379140}
(cherry picked from commit fde5de1bc63b656dabaafef3e5b59badcc613a22)
Review URL: https://codereview.chromium.org/1775933004 .
Cr-Commit-Position: refs/branch-heads/2623@{#604}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allow simple selectors which are not pseudo elements after ::content in
compound selectors. Polymer 0.5 content sometimes use ::content[attr]
instead of [attr]::content. This was made invalid with r369760.
R=timloh@chromium.org
BUG=589252
Review URL: https://codereview.chromium.org/1749713002
Cr-Commit-Position: refs/heads/master@{#378331}
(cherry picked from commit b9661ac4a6e7f0cfcd9b6fc8b25b074cac3b7bed)
Review URL: https://codereview.chromium.org/1771853005 .
Cr-Commit-Position: refs/branch-heads/2623@{#603}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
| |
Cr-Commit-Position: refs/branch-heads/2623@{#602}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
implementation.
BUG=401364
Review URL: https://codereview.chromium.org/1761303003
Cr-Commit-Position: refs/heads/master@{#379361}
(cherry picked from commit 587ba472dfefe862855487c4e6faee859b686160)
Review URL: https://codereview.chromium.org/1776003003 .
Cr-Commit-Position: refs/branch-heads/2623@{#601}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
| |
Cr-Commit-Position: refs/branch-heads/2623@{#600}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
TBR=chrishtr
BUG=590856
Fix merge conflict cleanup from https://codereview.chromium.org/1770913004
TBR=chrishtr
BUG=590856
Review URL: https://codereview.chromium.org/1775803003 .
Cr-Commit-Position: refs/branch-heads/2623@{#599}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
| |
Cr-Commit-Position: refs/branch-heads/2623@{#598}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|
|
|
|
|
|
|
|
|
|
| |
TBR=chrishtr
BUG=590856
Review URL: https://codereview.chromium.org/1778433002 .
Cr-Commit-Position: refs/branch-heads/2623@{#597}
Cr-Branched-From: 92d77538a86529ca35f9220bd3cd512cbea1f086-refs/heads/master@{#369907}
|