Revert 160495 "Currently Blink creates a fake run for a given is..."

This is a speculative revert. Karen notified me this afternoon
of a bad crasher on canary:
http://pastebin.com/GruVKNGm

which has been traced to
http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog_blink.html?url=%2Ftrunk&range=160594%3A160472&mode=html
Of that range, this looked most likely.

> Currently Blink creates a fake run for a given isolated span once during each call
> to createBidiRunsForLine. However in some cases the added fake run is not necessary.
> 
> This patch uses the same logic in RenderBlockFlow::appendRunsObject to create
> fake runs just when they are really needed.
> 
> Review URL: https://codereview.chromium.org/39783004

TBR=igor.o@sisa.samsung.com

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

git-svn-id: svn://svn.chromium.org/blink/trunk@160663 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Revert 160521 "Fix memory error during selector matching due to ..."

This is a speculative revert in hopes of fixing bug 311910.

This doesn't seem super related, but then again, none of the changes
in the regression range do.  We can roll this back in on Monday if
this fails to fix Canary.

According to Karen the regression range was:
http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog_blink.html?url=%2Ftrunk&range=160594%3A160472&mode=html

BUG=311910

> Fix memory error during selector matching due to getMatchedCSSRules.
> 
> The issue is that getMatchedCSSRules wasn't correctly pointing at its
> parent stylesheet, which meant that it didn't mark the style resolver
> as changed when it's selectorText was updated. This in turn meant that
> we had two RuleDatas for a rule that now only had one selector (i.e. it
> should only have one RuleData) and we'd try to access the selector at
> and index that didn't exist.
> 
> Instead, when creating the CSSOM weappers for getMatchedCSSRules,
> find the stylesheet corresponding to each rule and register the wrapper
> appropriately with it. We still need to leave in the codepath for
> lacking a sheet because we won't file a stylesheet for rules that are
> not CSSStyleRules (e.g. @import).
> 
> We also leave in the lacking a sheet codepath for the inspector.
> I'm not convinced the inspector code is correct, but this patch at
> least fixes the error that is accessible from JS.
> 
> BUG=297976
> 
> Review URL: https://codereview.chromium.org/25648002

TBR=ojan@chromium.org

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

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