compareDocumentPosition() should report PRECEEDING or FOLLOWING information even if nodes are disconnected

As per the latest specification, compareDocumentPosition() should report PRECEEDING or FOLLOWING
information even if nodes are disconnected:
- http://dom.spec.whatwg.org/#dom-node-comparedocumentposition

This behavior is consistent with both IE10 and Firefox 22.

Blink was not reporting PRECEEDING or FOLLOWING in all cases. This patches makes Blink behave
as expected.

BUG=263340
R=arv@chromium.org, haraken@chromium.org, tkent@chromium.org

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=154835

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

git-svn-id: svn://svn.chromium.org/blink/trunk@154908 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Revert 154887 "New positioning model: Borders"

This CL caused compile failures on Chrome OS build bots.
http://build.chromium.org/p/chromium.chrome/builders/Google%20Chrome%20ChromeOS/builds/56352/steps/compile/logs/stdio

> New positioning model: Borders
> 
> Converting to the shape coordinate system was not properly accounting
> for borders and padding. This has been fixed and a new convienence
> method added because of the added complexity of the conversion.
> 
> This is a port from WebKit: http://trac.webkit.org/changeset/153058
> 
> BUG=260357
> 
> Review URL: https://chromiumcodereview.appspot.com/20107003

TBR=bjonesbe@adobe.com

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

git-svn-id: svn://svn.chromium.org/blink/trunk@154909 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Rewrite the 'window.onerror' tests.

The tests are currently duplicating work all over the place, and are
difficult to update. This patch tries to bring some consistency to the
way the feature is tested in the hopes of making future improvements
simpler to effectively test.

R=ch.dumez@sisa.samsung.com

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

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