GitLab

In SQLite 3.10.2, the Unix VFS no longer defines unixCurrentTime(),
instead relying on unixCurrentTimeInt64(), which caused a crash in the
implementation of chromiumCurrentTime().  Add assertions to verify
required infrastructure at instantiation rather than first use.

BUG=580948,579743
R=michaeln@chromium.org

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

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

This CL removes a .css file that is no longer needed.  This
brings us closer to unifying the MD settings and helps migrate
away from the deprecated css import.

The .settings-box:first-of-type has been replaced by .first
or .vertical-list.  The .vertical-list is used with is="dom-repeat"
and .first is used where the the first element of the list
is explicit (rather than generated at run time).

BUG=537048

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

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

Add a new source type MENU_SOURCE_LONG_PRESS to identify context menu's being opened via the long press gesture.

For context, please refer to this patch https://codereview.chromium.org/1602903003/, where we display the context menu
on Windows when the long press gesture is released. This patch used the MENU_SOURCE_TOUCH source type in the context menu
params to determine whether a menu is being opened via the long press gesture. Turns out that the MENU_SOURCE_TOUCH is
used in places like devtools to open the context menu, which does not work due to the above patch.

Fix is to add a new menu source type MENU_SOURCE_LONG_PRESS We use this in RenderWidgetHostViewAura to identify context
menus opening via the long press gesture. Added another menu source type MENU_SOURCE_LONG_TAP which indicates menus
opening via the long tap gesture.

This should fix this regression.

BUG=581005
TEST=RenderWidgetHostViewAuraWithViewHarnessTest.ContextMenuTest. Updated this test to test for the MENU_SOURCE_LONG_PRESS gesture
type.

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

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

This update contains 1126(!) new sites, which is about 225/day since the last update. I've double-checked, and there seems to be nothing awry with the process. We're just getting that many submissions now.

BUG=
TBR=agl@chromium.org

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

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

  In order to roll GN 6a9b6b43..16920f1d (r370714:r371631) and pick up
  the following changes:

  81aa4e8f Add an assert_no_deps variable to GN.
  bf5ff790 Support for excluding variable from forwarding via forward_variables_form.

TBR=dpranke@chromium.org
CQ_EXTRA_TRYBOTS=tryserver.chromium.mac:mac_chromium_gn_dbg;tryserver.chromium.win:win8_chromium_gn_dbg,win_chromium_gn_x64_rel

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

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

- only keep two colors per category, one for "self" and one for "children";
- name them appropriately;
- drop gradients in legend swatches;
- replace explicitly colored borders with semi-transparent grey;
- fix legend for self time in pie chart summary.

BUG=580487

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

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

This CL is the first step to implement GATT service in Chrome for Windows by using cross platform testing fixture.

BUG=579202

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

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

No references are actually needed in the blink layer.

BUG=564965

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

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

BUG=577985

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

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

We text-align:left; our <li> elements so this shows up on live-sites that attempt
a text indent on their the list element's content.

BUG=568851

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

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

TBR=cmumford@chromium.org
BUG=459835

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

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

This is flakily crashing because it doesn't shut down
synchronously between tests, or so it seems.

Doesn't matter though because it's no longer necessary
for Mojo unless doing actual IPC.

R=lhchavez@chromium.org
BUG=None

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

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

This change makes the registration of in-process media service consistent with that of out-of-process service.

BUG=571155

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

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

We were missing the case where the first object in a multicol container was a
spanner (the call to previousSiblingMultiColumnSet() should have been
previousSiblingMultiColumnBox(), to catch spanner placeholders in addition to
column sets).

But instead of having a special code path depending on whether we're dealing
with the first box or not (to avoid subtracting the multicol container's top
border and padding from an uncalculated logical top of a column set), always
subtract the margin top edge of the first column box instead.

R=leviw@chromium.org

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

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

BUG=None
TBR=thakis@chromium.org
TBR=jam@chromium.org

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

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

Device scale factor impacts the draw properties (in particular, the
transforms of the TransformNodes in the property tree). So, mark that
draw properties need to be updated when device scale factor changes.

BUG=567832
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

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

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

After forcing tests to fail after a 10 seconds timeout, turns out the
spy promise tests are the culprit.
I have removed them from our tests as they are originally intended to
test XHR's and we now have a better API for that.

BUG=504204

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

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

BUG=577403

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

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

Compositor-workers currently do not support idle tasks (and so does not
have idle-task-runner). So idle-tasks should not be turned on for the
compositor workers' isolate. To fix this, move the code that turns on
idle tasks for the isolate into WorkerThread::initializeIsolate(), so
that compositor worker can choose to not do this for now.

BUG=565789, 430155

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

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

We capture sk picture from PictureLayer, which happens before we had
a chance to set the image decode controller during commit. The fix here
is not to use PlaybackToCanvas, but rather use other functions to
accomplish the same goal. PlaybackToCanvas should only be called after
commit.

R=enne
BUG=581107
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

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

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

Calling Layer::set_property_tree_sequence_number() does not set the
flag that a commit is needed, which means it can quickly get out of
date for layers that are not updated for other reasons when the Layer
is (de)serialized.

This CL makes the LayerTreeHost forcefully set the sequence number
to the same value as the current PropertyTrees.sequence_number, since
all valid in the hierarchy is valid at that point.

BUG=577352, 538710
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

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

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

BUG=536669

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

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

BUG=574938
TEST=PaintLayerPainterTest.PaintPhaseOutline
TEST=fast/multicol/span/outline.html

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

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

BUG=523278

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

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

The tool is run in parallel many times, so they may clobber each
other writing to the rewrite-sym.txt file. So add a rewrite-sym.lock
file that each instance grabs when writing.

Also attempts a windows implementation which is untested.

R=dcheng
BUG=578344

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

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

original cl:
https://codereview.chromium.org/1633713002/
revert:
https://codereview.chromium.org/1639603002/
reason:
broken paths

BUG=514857

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

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

The CVDisplayLink is tied to a ScopedTypeRef data member of DisplayLinkMac.
However, there may be other references. Since there's no guarantee that
~DisplayLinkMac() will invoke the last CVDisplayLinkRelease(..) and clear
the callback automatically, clear it explicitly in ~DisplayLinkMac.

BUG=564780

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

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

A recent commit broke the ability for the Google Cast and Media Router
extensions to start tab capture for mirroring.  The root cause was due
to the new behavior where the presence of deprecated constraints now
causes the getUserMedia() API to error-out (instead of silently ignoring
the constraints).

The short-term fix here is to simply filter out all goog* constraints
since they have no effect on tab capture.

BUG=579729
TBR=hta@chromium.org

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

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

BUG=581519
TBR=groby@chromium.org

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

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

Cross-process frames are possible in OOPIF-based webview.

BUG=578884

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

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

Pass to the renderer a list of texture targets, one per GpuMemoryBuffer
format, via a command line argument.
In this way GMBVFP can pick whatever GMB format it needs to use and bind
to the correct texture target.
This is similar to what we do for content (kContentImageTextureTarget).

kContentImageTextureTarget can't be used since the buffer usage could
differ from the buffer usage in GMBVFP.

Once all GMB formats supports persistent usage and we can consolidate
GPU_READ_CPU_READ_WRITE_PERSISTENT and GPU_READ_CPU_READ_WRITE this
code can go away and we can use just one command line switch.

BUG=524582

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

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

BUG=525873

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

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

BUG=525873

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

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

This still does not include cronet or webview.

BUG=580129

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

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

*PERF SHERRIF: this CL intentionally breaks dummy_benchmark.noisy_benchmark_1
for intergration testing purpose.
Please coordinate with prasadv@ before your revert this.

BUG=537676, 581465

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

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

The objects keeping their own WebURLLoaders (and thus being
WebURLLoaderClients) must promptly let go of their ownership upon
becoming garbage. Not doing so risks the embedder calling the client
while it is in a sweepable state.

R=
BUG=568173

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

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

BUG=525873

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

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

This allows us to use tracing agents that require more time to start.
The first use case of this will be the BattOr tracing agent, which
requires several round trips over USB before it can know whether
StartTracing was successful.

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

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

BUG=525873

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

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

Previously, when navigating from one page with 3+ infobars to another
page with infobars, the animation would show only one or two infobars
hiding then one or two infobars appearing, even though all the existing
infobars should disappear, then all the new infobars should appear. To
the user, it appeared as if some of the new infobars had been there all
along (peeking up in the back), which is confusing and wrong.

This strange behavior was caused by the logic for deciding when to show
a hiding or appearing animation. This logic didn't associate a
particular infobar with a particular view; it just ensured that the
number of views matched the number of infobars. So, if infobars were
removed and then new infobars were quickly added, there would be fewer
animations than expected.

The new code explicitly associates an infobar with each view, so if all
the infobars are removed and then several new ones added, the animations
will reflect that correctly.

BUG=396223

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

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