Only expose Notification.requestPermission() on the Window global.

Source/bindings/templates/interface_base.cpp

Index: Source/bindings/templates/interface_base.cpp
diff --git a/Source/bindings/templates/interface_base.cpp b/Source/bindings/templates/interface_base.cpp
index 04e6782ca7a7b43563018bb2f3a7a3580c0c7135..88586c46b259e03fe44db2508c4b32099d02663a 100644
--- a/Source/bindings/templates/interface_base.cpp
+++ b/Source/bindings/templates/interface_base.cpp
@@ -339,6 +339,10 @@ static void install{{v8_class}}Template(v8::Local<v8::FunctionTemplate> function
     ALLOW_UNUSED_LOCAL(instanceTemplate);
     v8::Local<v8::ObjectTemplate> prototypeTemplate = functionTemplate->PrototypeTemplate();
     ALLOW_UNUSED_LOCAL(prototypeTemplate);
+    {% if custom_registration_methods %}
+    ExecutionContext* context = currentExecutionContext(isolate);

[Peter Beverloo, 2015/08/28 15:58:58]

This will only be needed for *one* use of |custom_registration_methods| right
now - the one I'm introducing.

I don't know how performance sensitive this is, and would like your guidance on
whether this is OK, or we need more elaborate detection by iterating over
|custom_registration_methods| to determine any needs the context in the bindings
generator.

(Although presumably compilers will optimize this out?)

[haraken, 2015/08/29 08:04:57]

Would you help me understand where the context is used?

In terms of performance overhead, this would be no problem.

+    ALLOW_UNUSED_LOCAL(context);
+    {% endif %}
     {% if has_access_check_callbacks %}
     instanceTemplate->SetAccessCheckCallbacks({{cpp_class}}V8Internal::namedSecurityCheck, {{cpp_class}}V8Internal::indexedSecurityCheck, v8::External::New(isolate, const_cast<WrapperTypeInfo*>(&{{v8_class}}::wrapperTypeInfo)));
     {% endif %}