Skip some tests that should be rebaselined once the bots cycle

The bots were hosed and didn't run the tests. Those entries are
failing after r151269 on the try bots and will need to be
rebaselined once the bots cycle.

TBR=ojan@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@151322 bbb929c8-8fbe-4397-9dbb-9b2b20218538
First round of changes to correct exclusion tests that started failing when subpixel layout was turned off, and to correct some problems that disabling subpixel layout exposed.

This set of changes just corrects four tests. It also revises the subpixel-utils code to bring it into line with the most recent LayoutUnit et al changes and to simplify its use a little. The ExclusionPolygon appendArc() method was corrected, so that the 3rd of 5 additional vertices is in the center of the arc. The firstIncludedIntervalLogicalTop() methods now use ceiledLayoutUnit() to convert a float to a LayoutUnit within the shape.

BUG=237568
R=leviw@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@151323 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Make revalidation handling internal to CachedResource.

Also, move some ASSERTs from ResourceLoader to CachedResource that are
asserting CachedResource state.

BUG=none

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

git-svn-id: svn://svn.chromium.org/blink/trunk@151331 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Hide CSSSelectorList assignment operator to avoid memory leaks.

CSSSelectorList contains a pointer; assigning to an existing CSSSelectorList leaks the memory that was owned by that CSSSelectorList.

BUG=241892

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

git-svn-id: svn://svn.chromium.org/blink/trunk@151332 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove now-passing media tests from TestExpectations

TBR=ojan
BUG=222906,223562

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

git-svn-id: svn://svn.chromium.org/blink/trunk@151333 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Call cancelCompositionIfSelectionIsInvalid on setSelection.

Editor::cancelCompositionIfSelectionIsInvalid() only gets called when
Editor::respondToChangedSelection() is called, however is certain cases
(e.g. http://jsfiddle.net/LaNQ4/5/show/ ) the selection does not change
(just the offsets) and respondToChangedSelection() is not called.

On Linux, this bug can be seen when typing using ibus and JS deletes
the value of the focused field. The composition popup does not disappear.
Video before the change:
https://docs.google.com/a/google.com/file/d/0B-AevY72N_3qVE9BWGxsMnNId3M/edit?usp=sharing
Video after the change:
https://docs.google.com/a/google.com/file/d/0B-AevY72N_3qWWEwbmNmTnFHYWc/edit?usp=sharing

It also breaks Android typing too.

BUG=242715
TEST=editing/input/setting-input-value-cancel-ime-composition.html

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

git-svn-id: svn://svn.chromium.org/blink/trunk@151334 bbb929c8-8fbe-4397-9dbb-9b2b20218538
StringStats should track duplicates

This CL extends the STRING_STATS ifdef to record and dump information about
duplicate strings in the heap. Preliminary experiments with this information
seem to indiciate that there's lots of room for optimization here.

R=eseidel@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@151336 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Rework merging flakiness dashboard json to only parse the incremental JSON once.

-Parsing the incremental JSON takes time. No need to do it twice.
-This also lays the groundwork for fetching the aggregate json
in parallel with parsing the incremental json using ndb.
-Add a MockFile class in order to be able to test update_files instead
of just merge.
-Add the abilty to customize the builder name in the unittest json since
the builder name needs to match the one in the files.

R=dpranke@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@151337 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Fix crash when re-triggering a failed load via cloning inside DOMContentLoaded

BUG=244021
TEST=http/tests/misc/clone-in-DOMContentLoaded.html (under ASAN)

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

git-svn-id: svn://svn.chromium.org/blink/trunk@151338 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Teach WebString about 8 bit strings

Previously we always upconverted strings backing WebString to have both a 16
bit and an 8 bit buffer whenever we converted a WebString to a string16.
There's no reason to store a shadow 16 bit buffer in the String for this use
case. It's just as fast to copy out an 8 bit buffer into a string16 as it is to
copy out a 16 bit buffer.

This CL removes the vast majority of the string up converstions for Mobile
Gmail. In a future CL, we should remove WebString::data() to prevent Chromium
code from accidentially upconverting the underlying String.

R=brettw@chromium.org, eseidel@chromium.org, jamesr@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@151339 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Revert 151339 "Teach WebString about 8 bit strings"

It is breaking the build due to undefined symbols.

> Teach WebString about 8 bit strings
> 
> Previously we always upconverted strings backing WebString to have both a 16
> bit and an 8 bit buffer whenever we converted a WebString to a string16.
> There's no reason to store a shadow 16 bit buffer in the String for this use
> case. It's just as fast to copy out an 8 bit buffer into a string16 as it is to
> copy out a 16 bit buffer.
> 
> This CL removes the vast majority of the string up converstions for Mobile
> Gmail. In a future CL, we should remove WebString::data() to prevent Chromium
> code from accidentially upconverting the underlying String.
> 
> R=brettw@chromium.org, eseidel@chromium.org, jamesr@chromium.org
> 
> Review URL: https://codereview.chromium.org/15866003

TBR=abarth@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@151340 bbb929c8-8fbe-4397-9dbb-9b2b20218538
It was removed from the spec awhile ago, and was never implemented beyond
support for parsing the CSS property.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@151341 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Factor out blob to UTF-8 url/path conversion into helper functions.

TEST=run "webkit/tools/layout_tests/run_webkit_tests.sh --debug fast/files/null-origin-string.html --additional-drt-flag=--webcore-log-channels=FileAPI" and check stderr

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

git-svn-id: svn://svn.chromium.org/blink/trunk@151342 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Modify w3c import script to be able to run over a whole repo.

This change allows us to run the import script over a whole repo, rather
than just the 'submitted' and 'accepted' sub directories. This is another
step towards being able to import and run the repos wholesale, rather than
piecemeal.

Most of the changes in this patch involve changes to handle malformed input files, log them, and continue. We need to continue to make things more robust here, and should start to add tests for this, but I'll defer this for now.

Given that ultimately my goal is to make the import processes simpler rather than more complex, I want to defer writing tests for stuff I'm trying to delete. Once I get closer to have the script actually in the form we'll want long-term, and we'll want to support this properly, I'll make sure we have tests (right now, I'm the only one playing around with this).

R=ojan@chromium.org
BUG=

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

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