Changes between Version 69 and Version 70 of WebKitIDL

Timestamp:

May 21, 2012 8:28:06 PM (12 years ago)

Author:

morrita@google.com

Comment:

--

WebKitIDL

@@ -31 +31 @@
  - [#Conditional Conditional(i,m,a)][[br]]
  - [#V8EnabledAtRuntime V8EnabledAtRuntime(i,m,a)][[br]]
+ - [#V8EnabledPerContext V8EnabledPerContext(i,m,a)][[br]]
  - [#CustomToJSObject CustomToJSObject(i), JSCustomToJSObject(i), V8CustomToJSObject(i)][[br]]
  - [#CheckSecurity CheckSecurity(i), DoNotCheckSecurity(m,a), DoNotCheckSecurityOnGetter(a), DoNotCheckSecurityOnSetter(a)][[br]]
@@ -1051 +1052 @@
 it means that [V8EnabledAtRuntime] is specified on all the attributes and methods of the interface,
 
+== [V8EnabledPerContext](i,m,a) == #V8EnabledAtRuntime
+
+Summary: In Chromium/V8, you can enable or disable a flag per execution context (that is DOMWindow).
+
+If you specify [V8EnabledPerContext], you need to write "flag-binding" code
+in WebCore/bindings/generic/ContextEnabledFeatures.h, WebCore/bindings/generic/ContextEnabledFeatures.cpp
+The implementation can choose arbitrary decision logic. A typical approach is to ask FrameLoaderClient about its availability.
+
+Currently, V8EnabledPerContext is only effective for attributes on DOMWindow.
+
 == [CustomToJSObject](i), [JSCustomToJSObject](i), [V8CustomToJSObject](i) == #CustomToJSObject