Avoid duplication of calling getTransformedClipBounds in stroke APIs.

We can avoid duplication of calling getTransformedClipBounds by using computeDirtyRect which takes three arguments.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@171733 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Document.dir should reflect the 'dir' attribute of the root html element

Document.dir should reflect the 'dir' attribute of the root html element as per
the specification:
http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#dom-document-dir

Previously, Chromium was reflecting the the 'dir' attribute of the body
element. The new behavior is consistent with Firefox 28 and IE11.

R=arv@chromium.org,tkent@chromium.org
BUG=363107
TEST=fast/dom/document-dir-property.html

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

git-svn-id: svn://svn.chromium.org/blink/trunk@171734 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Web Animations: Fix test for Element destructor clean-up

This fixes a small typo in a test introduced in crrev.com/236833002. The
test checks that an animation's target member is cleared upon element
destruction, but I forgot to actually set the target initially on the
animation.

BUG=362404

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

git-svn-id: svn://svn.chromium.org/blink/trunk@171735 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove style check for comparison to zero

Keeps comparison to true/false and null/non-null, hence renaming test to
[readability/comparison_to_boolean]

Per discussion:
Can we lose readability/comparison_to_zero?
https://groups.google.com/a/chromium.org/d/topic/blink-dev/3HVOC-5mFxE/discussion

Docs updated:
http://www.chromium.org/blink/coding-style#TOC-Null-false-and-0

TEST=test-webkitpy

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

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