$location causes JS errors on Chrome in conjunction with SVG

[eekboom]

SVGElementInstances are created when you use "use" element in SVG to wrap the original element.
An SVGElementInstance has no "nodeName" property, which causes a click handler in the $locationProvider to fail.
SSCCE at http://plnkr.co/edit/HpiObOlF2MESe9OiRncW

See also disconnectme/disconnect#228

Other browsers seem to use the "use" element itself in event handling, so that the error does not happen there.
I am not really sure what the spec-compliant handling would be here, but it should be easy to work around in angular itself (for example using "correspondingUseElement" property).

[caitp]

ugh svg, causing so many problems =)

so I don't think we actually want the click handler to follow this link because the xlink:href is just linking to a different element, we want this to abort.

Would you care to submit a patch to fix this? It should be pretty simple (although I have said that before and turned out to be incorrect in the past)

[caitp]

You know what, I think we shouldn't worry about this, it looks like this has been fixed: https://src.chromium.org/viewvc/blink?revision=176090&view=revision

It's kind of a pain for the remaining months until people are using Chrome 37, but I guess it's ok

[caitp]

/cc @IgorMinar unless you think we should accomodate buggy versions of chrome, in which case the workaround is pretty trivial

[eekboom]

Ah, thanks for researching that!
That's fine with me: It doesn't really break anything for now and if it's fixed in the next Chrome version that's great!

[metamatt]

This is still a problem for Safari, including Safari 8.

[uriklar]

Also for IE. See #10078