Changes between Version 69 and Version 70 of WebKitIDL


Ignore:
Timestamp:
May 21, 2012 8:28:06 PM (9 years ago)
Author:
morrita@google.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WebKitIDL

    v69 v70  
    3131 - [#Conditional Conditional(i,m,a)][[br]]
    3232 - [#V8EnabledAtRuntime V8EnabledAtRuntime(i,m,a)][[br]]
     33 - [#V8EnabledPerContext V8EnabledPerContext(i,m,a)][[br]]
    3334 - [#CustomToJSObject CustomToJSObject(i), JSCustomToJSObject(i), V8CustomToJSObject(i)][[br]]
    3435 - [#CheckSecurity CheckSecurity(i), DoNotCheckSecurity(m,a), DoNotCheckSecurityOnGetter(a), DoNotCheckSecurityOnSetter(a)][[br]]
     
    10511052it means that [V8EnabledAtRuntime] is specified on all the attributes and methods of the interface,
    10521053
     1054== [V8EnabledPerContext](i,m,a) == #V8EnabledAtRuntime
     1055
     1056Summary: In Chromium/V8, you can enable or disable a flag per execution context (that is DOMWindow).
     1057
     1058If you specify [V8EnabledPerContext], you need to write "flag-binding" code
     1059in WebCore/bindings/generic/ContextEnabledFeatures.h, WebCore/bindings/generic/ContextEnabledFeatures.cpp
     1060The implementation can choose arbitrary decision logic. A typical approach is to ask FrameLoaderClient about its availability.
     1061
     1062Currently, V8EnabledPerContext is only effective for attributes on DOMWindow.
     1063
    10531064== [CustomToJSObject](i), [JSCustomToJSObject](i), [V8CustomToJSObject](i) == #CustomToJSObject
    10541065