Changes between Version 80 and Version 81 of WebKitIDL

Timestamp:

Nov 26, 2012, 11:14:16 PM (12 years ago)

Author:

haraken@chromium.org

Comment:

--

WebKitIDL

@@ -33 +33 @@
  - [#V8EnabledAtRuntime V8EnabledAtRuntime(i,m,a)][[br]]
  - [#V8EnabledPerContext V8EnabledPerContext(i,m,a)][[br]]
- - [#CustomToJSObject CustomToJSObject(i), JSCustomToJSObject(i), V8CustomToJSObject(i)][[br]]
+ - [#CustomToJSObject CustomToJSObject(i), JSCustomToJSObject(i), V8CustomToJSObject(i), SuppressToJSObject(i)][[br]]
  - [#CheckSecurity CheckSecurity(i), DoNotCheckSecurity(m,a), DoNotCheckSecurityOnGetter(a), DoNotCheckSecurityOnSetter(a)][[br]]
  - [#CheckSecurityForNode CheckSecurityForNode(m,a)][[br]]
@@ -1112 +1112 @@
 Currently, V8EnabledPerContext is only effective for attributes on DOMWindow.
 
-== [CustomToJSObject](i), [JSCustomToJSObject](i), [V8CustomToJSObject](i) == #CustomToJSObject
+== [CustomToJSObject](i), [JSCustomToJSObject](i), [V8CustomToJSObject](i), [SuppressToJSObject](i) == #CustomToJSObject
 
 Summary: They allow you to write custom toJS() or toV8().
@@ -1146 +1146 @@
     }
 }}}
+ * With [SuppressToJSObject], even the declarations of toJS()/toV8() are not generated. If you want to make sure that someone never calls toJS()/toV8(), you can use [SuppressToJSObject]. You might want to use [SuppressToJSObject] for mixins, where toJS()/toV8() won't work as expected.
 
 == [CheckSecurity](i), [DoNotCheckSecurity](m,a), [DoNotCheckSecurityOnGetter](a), [DoNotCheckSecurityOnSetter](a) == #CheckSecurity