Make Theme forget about Font.

It should use FontDescription instead.

R=eae
BUG=315783

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

git-svn-id: svn://svn.chromium.org/blink/trunk@162783 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Fix for broken undo functionality

When delete(character granularity) is performed after few text insertions,
this delete command is added to already open typing command. This was
resulting in wrong 'undo' behaviors.

This can be fixed by keeping continuous delete operations alone as a group.
Hence whenever a delete command follows some other typing command say text
insertion, we should open a new typing command.

This fixes many erroneous behaviors related to undo operation.

TEST=LayoutTests/editing/undo/undo-insert-delete.html

BUG=319659

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

git-svn-id: svn://svn.chromium.org/blink/trunk@162784 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Made SelectorChecker::match to return matched selector's specificity for :host.
    
The specificity of a :matches() pseudo-class is the specificity of the most specific complex selector that matched.
c.f. http://www.w3.org/TR/selectors4/#specificity
    
:host() pseudo-class works in almost the same way as :matches().
So the specificity of :host() pseudo-class should be the specificity of the most specific complex selector that matched.
    
To do so, CSSSelector::specificity ignores :host() pseudo-class and SelectorChecker calculates :host()'s specificity.
(c.f. the spec says :not() or :matches() pseudo-class itself does not contribute any additional specificity)
    
When comparing matched rules, see both CSSSelector::specificity() and specificity calculated by SelectorChecker::match().
    
BUG=320697
TEST=fast/dom/shadow/host-pseudo-class.html

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

git-svn-id: svn://svn.chromium.org/blink/trunk@162785 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Disable DidWriteToInitialDocumentBeforeModalDialog on Windows.

Like DidAccessInitialDocumentBodyBeforeModalDialog, this test appears to
be failing only on the WebKit XP (deps) bot.

BUG=312192

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

git-svn-id: svn://svn.chromium.org/blink/trunk@162786 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Call AtomicString::number() in CSSGrammar.y

Call AtomicString::number() in CSSGrammar.y instead of String::number as
CSSSelector::setArgument() expects an AtomicString in argument. This
avoids uselessly creating a String and then convert it to an AtomicString.

R=eseidel
BUG=323739

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

git-svn-id: svn://svn.chromium.org/blink/trunk@162787 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Make StyleSheetInsert a more realistic perf test.

This was testing inserting stylesheets in a page with no style
recalc. Instead, force a recalc before and after the stylesheet
inserts to make it better match what a real page would look like.

BUG=323732

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

git-svn-id: svn://svn.chromium.org/blink/trunk@162788 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Have CSSFontFeatureValue store the tag as an AtomicString instead of a String

Have CSSFontFeatureValue store the tag as an AtomicString instead of a String.
CSSFontFeatureValue objects are constructed in:
- CSSParser::parseFontFeatureTag() where the tag is a CSSParserString that can
be easily be used to construct either a String or an AtomicString
- CSSComputedStyleDeclaration::getPropertyCSSValue() where it is constructed
from a FontFeature. FontFeature stores the tag as an AtomicString.

CSSFontFeatureValue::tag() getter is used by:
- FontBuilder::setFeatureSettingsValue() to construct a FontFeature object,
which requires the tag as a AtomicString and thus required us to convert
the tag from String to AtomicString.
- CSSFontFeatureValue::customCSSText() which uses StringBuilder::append(), so
it does not matter if the tag is a String or AtomicString.
- CSSFontFeatureValue::equals() for comparing the tags of 2 CSSFontFeatureValue
objects. In this case, keeping the tag as AtomicString would be more efficient.

Therefore, by having CSSFontFeatureValue store the tag as an AtomicString, we
gain consistency with FontFeature, which is important as we need 2-way conversion
from CSSFontFeatureValue <-> FontFeature. Also, it makes
CSSFontFeatureValue::equals() faster.

R=eseidel
BUG=323739

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

git-svn-id: svn://svn.chromium.org/blink/trunk@162789 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Mark http/tests/media/media-source/webkitmediasource-removesourcebuffer-texttrack.html as crashy

BUG=324120
TBR=
NOTRY=true

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

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