Add error dispatch events to SVGStyleElement

Source/core/html/HTMLStyleElement.cpp

Index: Source/core/html/HTMLStyleElement.cpp
diff --git a/Source/core/html/HTMLStyleElement.cpp b/Source/core/html/HTMLStyleElement.cpp
index 2d6b0366b2c7dfb82f4dc3a313d291c0a170a04d..b169020abd187730862e1df95edb3b59fa79acb7 100644
--- a/Source/core/html/HTMLStyleElement.cpp
+++ b/Source/core/html/HTMLStyleElement.cpp
@@ -143,7 +143,7 @@ void HTMLStyleElement::dispatchPendingEvent(StyleEventSender* eventSender)
 
 void HTMLStyleElement::notifyLoadedSheetAndAllCriticalSubresources(LoadedSheetErrorStatus errorStatus)
 {
-    if (m_firedLoad)
+    if (m_firedLoad && errorStatus == NoErrorLoadingSubresource)

[pdr., 2015/03/31 03:01:43]

This looks like it can lead to firing more than one load event.

[jww, 2015/03/31 21:31:42]

I'm fairly sure this is correct, but double check my reasoning :-) If it's a
load event, then errorStatus will be NoErrorLoadingSubresource, in which case if
one has already fired, m_firedLoad will be true, and this condition will hold,
this returning early. Otherwise, if the event being fired is *not* a load event
(namely if it's an error), the condition will fail, and it will not return
early.

A convoluted way of saying that the only way to not return early is that a load
has not fired yet *and* the event *isn't* a load.

[fs, 2015/04/01 08:47:50]

Maybe something like:

bool sheetWasLoaded = errorStatus == NoErrorLoadingSubresource;
if (m_firedLoad && sheetWasLoaded)
    return;
m_loadedSheet = ...;

would make it feel less convoluted.

         return;
     m_loadedSheet = (errorStatus == NoErrorLoadingSubresource);
     styleLoadEventSender().dispatchEventSoon(this);