Throw an exception when denying access to 'Frame's 'location' setter.

Source/core/dom/ErrorEvent.h

 /*
  * Copyright (C) 2009 Google Inc. All rights reserved.
  *
  * Redistribution and use in source and binary forms, with or without
  * modification, are permitted provided that the following conditions are
  * met:
  *
  *     * Redistributions of source code must retain the above copyright
  * notice, this list of conditions and the following disclaimer.
  *     * Redistributions in binary form must reproduce the above
@@ skipping 47 matching lines @@
     static PassRefPtr<ErrorEvent> create(const AtomicString& type, const ErrorEventInit& initializer)
     {
         return adoptRef(new ErrorEvent(type, initializer));
     }
     static PassRefPtr<ErrorEvent> createSanitizedError()
     {
         return adoptRef(new ErrorEvent("Script error.", String(), 0, 0));
     }
     virtual ~ErrorEvent();
 
-    const String& message() const { return m_message; }
+    // As 'message' is exposed to JavaScript, prefer 'sanitizedMessage()' when present.
+    const String& message() const { return !sanitizedMessage().isEmpty() ? sanitizedMessage() : unsanitizedMessage(); }

[abarth-chromium, 2013/08/14 19:42:08]

Woah, I don't think we should fall back to the sanitized message.  Can't we just
ASSERT that sanitizedMessage is always non-empty if there is a
unsanitizedMessage?

     const String& filename() const { return m_fileName; }
     unsigned lineno() const { return m_lineNumber; }
     unsigned colno() const { return m_columnNumber; }
 
+    // 'messageForConsole' is not exposed to JavaScript, and prefers 'unsanitizedMessage()'.
+    const String& messageForConsole() const { return !unsanitizedMessage().isEmpty() ? unsanitizedMessage() : sanitizedMessage(); }

[abarth-chromium, 2013/08/14 19:42:08]

Fallback here makes sense.

+
     virtual const AtomicString& interfaceName() const;
 
+    void setUnsanitizedMessage(const String&);
+
 private:
     ErrorEvent();
     ErrorEvent(const String& message, const String& fileName, unsigned lineNumber, unsigned columnNumber);
     ErrorEvent(const AtomicString&, const ErrorEventInit&);
 
-    String m_message;
+    const String& unsanitizedMessage() const { return m_unsanitizedMessage; }
+    const String& sanitizedMessage() const { return m_sanitizedMessage; }

[abarth-chromium, 2013/08/14 19:42:08]

What's the point of these private accessors?  Code that can see these can see
the member variables too.

+
+    String m_unsanitizedMessage;
+    String m_sanitizedMessage;
     String m_fileName;
     unsigned m_lineNumber;
     unsigned m_columnNumber;
 };
 
 } // namespace WebCore
 
 #endif // ErrorEvent_h