Enable inspector/report-protocol-errors.html for content shell

The problem that caused its failure was fixed in https://codereview.chromium.org/14079008/

BUG=231934

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

git-svn-id: svn://svn.chromium.org/blink/trunk@148832 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Fix the grid-{end|after} position resolution

Our resolution code was resolving both positions in the same way
but that doesn't work: in grid-rows: 2 / 3, the 2 lines, even if
they are different numbers, refers to the same grid position so
using the same formula to resolve them cannot work.

Because of the previous issue, we were off-by-one when resolving
grid-{end|after}. This only fixes positive explicit position as
the negative case needs more testing and scaffolding.

BUG=231695
TEST=fast/css-grid-layout/grid-item-spanning-resolution.html

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

git-svn-id: svn://svn.chromium.org/blink/trunk@148833 bbb929c8-8fbe-4397-9dbb-9b2b20218538
DevTools: beautify Timeline status bar

BUG=234184

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

git-svn-id: svn://svn.chromium.org/blink/trunk@148834 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove unused file InlineASM.h

BUG=none
TEST=wktry compiles

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

git-svn-id: svn://svn.chromium.org/blink/trunk@148835 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove shouldUseCredentialStorage callbacks, push down the StoredCrendtials
policy instead.

BUG=none
TEST=none

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

git-svn-id: svn://svn.chromium.org/blink/trunk@148836 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Fix grid-item-spanning-resolution-expected.txt after r148833

It was missing an extra 'PASS'

TBR=ojan
BUG=231695

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

git-svn-id: svn://svn.chromium.org/blink/trunk@148837 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Add UseCounter for SVGTRefElement

One option for fixing SVGTRefElement's usage of MutationEvents
is to delete it (it's not well-supported in Blink anyway, as it
supports only a subset of the specced features). Collecting
usage information will help evaluate whether that's a viable
strategy.

R=ojan
BUG=231592

Review URL: https://chromiumcodereview.appspot.com/14188033

git-svn-id: svn://svn.chromium.org/blink/trunk@148838 bbb929c8-8fbe-4397-9dbb-9b2b20218538
BUG=228782

Add support for computing the shape-outside shape-margin boundary for a polygon. This change is similar to the one added for padding polygons, see bug https://bugs.webkit.org/show_bug.cgi?id=112592. The algorithm used for computing the margin boundary is is provisional. It works correctly for convex polygons and will work correctly for non self-intersecting polygons whose margin boundary is the same shape as the original polygon.

Review URL: https://chromiumcodereview.appspot.com/14220005

git-svn-id: svn://svn.chromium.org/blink/trunk@148839 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Switch RegularExpression from YARR to V8

Make RegularExpression use V8 instead of YARR. This removes all but one
last usage of YARR in ContentSearchUtils which can be removed in a follow
up patch.

It's a little awkward to use V8's regular expression features from C++ since
you need to interact with the JS object fields, but this is the best we can do
for now. Eventually it'd be nice if V8 exposed a RegExp API directly.

This patch also fixes a bug identified in the process of writing a test where
having an invalid regex in the pattern attribute on an <input> results in an
input that can never be valid. Instead we should ignore the attribute.

http://www.whatwg.org/specs/web-apps/current-work/multipage/common-input-element-attributes.html#the-pattern-attribute

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

git-svn-id: svn://svn.chromium.org/blink/trunk@148840 bbb929c8-8fbe-4397-9dbb-9b2b20218538