rewrite spec links with http: to https: and fix known Javascript redirected links

third_party/WebKit/Source/core/svg/SVGElement.idl

Index: third_party/WebKit/Source/core/svg/SVGElement.idl
diff --git a/third_party/WebKit/Source/core/svg/SVGElement.idl b/third_party/WebKit/Source/core/svg/SVGElement.idl
index e892a8e41bef813ac94a9df10b1ce5ebf81da6ff..e51cb29a40e85ea0e914e101a56d197f8864e26c 100644
--- a/third_party/WebKit/Source/core/svg/SVGElement.idl
+++ b/third_party/WebKit/Source/core/svg/SVGElement.idl
@@ -20,13 +20,13 @@
  * Boston, MA 02110-1301, USA.
  */
 
-// http://www.w3.org/TR/SVG2/types.html#InterfaceSVGElement
+// https://www.w3.org/TR/SVG2/types.html#InterfaceSVGElement

[foolip, 2016/12/02 09:55:29]

We'll have to do something with all the /TR/SV2/ links, but not in this CL.

[Mark Dittmer, 2016/12/02 14:05:45]

+foolip@chromium.org: RSVP (here or via email) as in, we should be scraping them
in tooling, or the need to be rewritten to point elsewhere?

[foolip, 2016/12/02 14:45:33]

This one should be https://svgwg.org/svg2-draft/types.html#InterfaceSVGElement I
think, but asking SVG folks (pdr@, fs@opera.com) would be good.

There are some /TR/SVG11/ links, but none to svgwg.org AFAICT. In any event,
linking to just the spec that's maintained is the idea, but no need to
prioritize until we see that SVG data isn't right, or if there's conflicting
data from different copies.

 
 interface SVGElement : Element {
     [MeasureAs=SVGClassName] readonly attribute SVGAnimatedString className;
     [SameObject, PerWorldBindings] readonly attribute DOMStringMap dataset;
     // CSS Object Model (CSSOM)
-    // http://dev.w3.org/csswg/cssom/#the-elementcssinlinestyle-interface
+    // https://dev.w3.org/csswg/cssom/#the-elementcssinlinestyle-interface
     [SameObject, PutForwards=cssText] readonly attribute CSSStyleDeclaration style;
 
     readonly attribute SVGSVGElement? ownerSVGElement;