SVG: Move/rename reference management to SVGElement

No change in logic, but rename and move.

I used different naming convensions based on suggestions by fs@opera.com :
"referencingElements" is renamed "outgoingReferences", and
"referencedElements" is renamed "incomingReferences".

- |SVGDocumentExtensions::setOfElementsReferencingTarget|
  moved to |SVGElement::setOfIncomingReferences|
- |SVGDocumentExtensions::addElementReferencingTarget|
  moved to |SVGElement::addOutgoingReferenceTo|
- |SVGDocumentExtensions::removeAllTargetReferencesForElement|
  moved to |SVGElement::removeAllOutgoingReferences|
- |SVGDocumentExtensions::rebuildAllElementReferencesForTarget|
  moved to |SVGElement::rebuildAllIncomingReferences|
- |SVGDocumentExtensions::removeAllElementReferencesForTarget|
  moved to |SVGElement::removeAllIncomingReferences|

Changes to files SVG\w+Element.cpp made by a sed script:
s/document()\.accessSVGExtensions()\.addElementReferencingTarget(this, \([a-Z()\*]\+\))/addOutgoingReferenceTo(\1)/g
s/document()\.accessSVGExtensions()\.removeAllTargetReferencesForElement(this)/removeAllOutgoingReferences()/g
s/document()\.accessSVGExtensions()\.setOfElementsReferencingTarget(this)/setOfIncomingReferences()/g

BUG=378670

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177039 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove mousedown preconnect from WebPrescientNetworking

Its implementation is already removed from chromium in r279633.

BUG=386888

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177040 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Move attributes-related methods from ElementData to AttributeCollection

Move attributes-related methods from ElementData to AttributeCollection.
Now that we have a dedicated class for Element attributes, it seems odd for
the attributes-related API to be in Element / ElementData.

This CL does not change the Element API for attributes so that the patch
stays small. However, the idea would be to later move callers away from the
attributes API on Element and instead call Element::attributes() and then
interact directly with the returned AttributeCollection object.

Using AttributeCollection directly has the benefit of avoiding redundant
calls to ElementData::isUnique() and the caller can store AttributeCollection
object in a variable and then any later interaction with this object won't
require checking if ElementData is unique or not.

R=esprehn@chromium.org, adamk@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177041 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Add a unit test for WebCore::GlyphBuffer.

This class is fairly simple, but it's worth taking the rare opportunity
to add a unit test to Blink.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177042 bbb929c8-8fbe-4397-9dbb-9b2b20218538
WebLeakDetector: Fix false positive leaks on worker tests when oilpan is enabled.

This patch adds another round of GC to make sure Document is destroyed after |WorkerMessagingProxy::workerObjectDestroyed|.

BUG=389042

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177043 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Don't preload all tokens

Turns out we're not really ready to do this.
The preloader has lots of bugs at least in the
re-use-existing-preload logic. Yes, we should fix
these bugs. Yes, making all tokens go through the
preloader would force us to fix these bugs. But
until we do, it seems better to sweep them back
under the rug (and just have flakiness in the wild)
rather than making preloader bugs completely
unavoidable by forcing every token through it.

This is a partial revert of:
https://codereview.chromium.org/302063002/

BUG=356292,388308,389226

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177044 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Use HTMLMediaElement's helpers for the controls fullscreen button

This isolates ExemptIFrameAllowFullScreenRequirement to a single call
site and makes the code more readable.

R=acolwell@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177045 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Change port to use apache by default on win7, update test expectations.

This switches the default on Win 7 to use the native Win32 version of Apache
2.2 instead of LigHTTPd.  In theory Apache will substantially more stable
and also probably faster. I am hoping that this fixes the situation in bug
378444 where the server just doesn't work on some runs as well.

We also match more of the test expectations on other platforms.

If this change sticks and does improve flakiness, we'll try switching XP
as well in a later change.

This change also deletes all of the FlakyTest entries for http tests
on Win7, so that we can better get a real sense of the flakiness.

R=ojan@chromium.org
BUG=378444, 30536

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

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