Re: Testing Requirements

On 6/3/11, Philippe Le Hegaret <plh@w3.org> wrote:


> You now have:
One more list to unsubscribe from.

>  http://www.w3c-test.org:81/
>  http://www.w3c-test.org:82/
>  http://www.w3c-test.org:83/
>

| function assert_readonly(object, property_name, description)
|     {
|          var initial_value = object[property_name];
|          try {
|              var message = make_message(
|                  "assert_readonly", description,
|                  "deleting property ${p} succeeded", {p:property_name});
|
| // (GS) REmemer, delete will result `true` if p doesn't have that property.
| // (GS) so javascript: alert( delete ({}).toString) will result `true`.
| // Since DOM readonly is often impl'd as a getter in the object's prototype,
| // delete o[p] may result true, though the getter `p` remains.
|              assert(delete object[property_name] === false, message);

(unsubscribes...)
-- 
Garrett