Calling isRenderedTable() instead of isTable() to maintain consistency within the Editing module.

Instead of doing the isTable() check on a node's renderer, we can directly
use the htmlediting method isRenderedTable() that internally carries out
the same check.

This is to maintain consistency within the editing code.

htmlediting defines two methods: isRenderedTable() and isTableElement()
to perform a check based on the renderer, or the tag name respectively.
Within the editing module, these methods should be called where required.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@162709 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Reset test expectations after GURL data URL changes

This is a follow up to crrev.com/r236917 - resolving '#foo' is
now supported on all schemes.
The test cases changed have been unaltered in 4 years since added in
https://bugs.webkit.org/attachment.cgi?id=55151&action=diff
they have never PASSed on the upstream WebKit KURL implementation;
as GURL is now consistent with KURL I am reworking the tests to expect
this outcome rather than mark GURL as FAILing these tests. (The same
change could reasonably be applied in the webkit.org tree too).

BUG=322887,291747

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

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