Changes between Version 101 and Version 102 of WebKitIDL

Timestamp:

May 8, 2013, 1:35:06 AM (13 years ago)

Author:

Christophe Dumez

Comment:

Remove V8Unforgeable and V8OnProto

WebKitIDL

@@ -21 +21 @@
  - [#Deletable Deletable(a), NotEnumerable(a)][[br]]
  - [#CachedAttribute CachedAttribute(a)][[br]]
- - [#V8Unforgeable V8Unforgeable(m,a), V8OnProto(m,a)][[br]]
  - [#URL URL(a)][[br]]
  - [#JSWindowEventListener JSWindowEventListener(a)][[br]]
@@ -658 +657 @@
 In addition, setters always need to invalidate the cache.
 
-== `[V8Unforgeable]`(m,a), `[V8OnProto]`(m,a) == #V8Unforgeable
-
- * [http://dev.w3.org/2006/webapi/WebIDL/#Unforgeable The spec of Unforgeable]
-
-Summary: They control where a getter/setter of a given attribute is defined.
-
-Usage: They can be specified on methods or attributes:
-{{{
-    [V8Unforgeable] void func();
-    attribute [V8OnProto] DOMString str;
-}}}
-
-By default in JSC and V8, attribute getters/setters are defined on a DOM object, and methods are defined on a prototype chain 
-(although the Web IDL spec requires that both attribute getters/setters and methods should be defined on a prototype chain).
-
-If you want to explicitly control where an attribute getter/setter or a method is defined in V8,
-you can use `[V8Unforgeable]` or `[V8OnProto]`.
-
- * `[V8Unforgeable]` indicates that an attribute getter/setter or a method should be defined on a DOM object.
- * `[V8OnProto]` indicates that an attribute getter/setter or a method should be defined on a prototype chain.
-
-Note: As explained above, the current implementation of JSC and V8 is wrong with the Web IDL spec,
-and `[V8Unforgeable]` and `[V8OnProto]` are used for hack.
-You should not use them unless you have a strong reason to use them.
-
 == `[URL]`(a) == #URL