[webcrypto] Fix a bad test.

The test was throwing an exception due to a syntax error.

BUG=245025

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

git-svn-id: svn://svn.chromium.org/blink/trunk@163284 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Change isBlock and isInline functions to check for isElementNode

Simple refactoring to add isElementNode check in isBlock and isInline functions.
Also removed isElementNode check from enclosingBlock.

Webkit bug pointing the same - https://bugs.webkit.org/show_bug.cgi?id=86106

TEST=Refactoring, no behavior change.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@163285 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Promise.then should not throw a TypeError on ground of parameters.

Promise.prototype.then should not throw a TypeError if non-callable
values (e.g. as null, 0, "hello") are given.

BUG=326093

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

git-svn-id: svn://svn.chromium.org/blink/trunk@163286 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Add 'exposed' objects and embeds to a document's named properties.

The spec tells us that exposed <embed> and <object> are to be included
in a document's "supported property names"

  http://www.whatwg.org/specs/web-apps/current-work/#dom-document-nameditem
  http://www.whatwg.org/specs/web-apps/current-work/#exposed

(along with various other side conditions.) 

crbug.com/313292 retired a partial notion of "exposed"ness, this
provides an implementation close to the spec's definition.

R=
BUG=316988

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

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