W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2013

[Bug 21073] merge [Unforgeable] and readonly into unforgeable

From: <bugzilla@jessica.w3.org>
Date: Thu, 21 Feb 2013 15:47:50 +0000
To: public-script-coord@w3.org
Message-ID: <bug-21073-3890-YKeCSbnsLh@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21073

--- Comment #3 from Boris Zbarsky <bzbarsky@mit.edu> ---
But in general there is no reason to restrict unforgeable to readonly
properties; it can make sense for operations and writable properties too, as
the Location example shows.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 21 February 2013 15:47:52 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:09 UTC