Deprecate invoking the default action for untrusted events.

third_party/WebKit/Source/core/frame/Deprecation.cpp

 // Copyright 2016 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "core/frame/Deprecation.h"
 
 #include "core/dom/Document.h"
 #include "core/dom/ExecutionContext.h"
 #include "core/frame/FrameConsole.h"
 #include "core/frame/FrameHost.h"
@@ skipping 370 matching lines @@
 
     case UseCounter::During_Microtask_Prompt:
         return willBeRemoved("Invoking 'prompt()' during microtask execution", 53, "5647113010544640");
 
     case UseCounter::During_Microtask_SyncXHR:
         return willBeRemoved("Invoking 'send()' on a sync XHR during microtask execution", 53, "5647113010544640");
 
     case UseCounter::MediaStreamOnEnded:
         return replacedWillBeRemoved("The MediaStream 'ended' event", "the MediaStream 'inactive' event", 53, "5730404371791872");
 
+    case UseCounter::UntrustedEventDefaultHandled:
+        return willBeRemoved("Performing default actions on untrusted events", 53, "5718803933560832");

[Rick Byers, 2016/05/17 17:34:28]

I'm a little worried that developers may see this even when they're doing
nothing wrong (eg. there happens to be a default action as a side effect of an
event they're generating but they don't rely on it).  How about changing the
wording to something like this:

"A DOM event generated from JavaScript has triggered a default action inside the
browser.  This behavior is non-standard and will be removed in M53.  See ...".?

[dtapuska, 2016/05/17 19:32:42]

Done.

+
     // Features that aren't deprecated don't have a deprecation message.
     default:
         return String();
     }
 }
 
 } // namespace blink