This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21073 - merge [Unforgeable] and readonly into unforgeable
Summary: merge [Unforgeable] and readonly into unforgeable
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Cameron McCormack
QA Contact: public-webapps-bugzilla
Depends on:
Reported: 2013-02-21 15:42 UTC by Anne
Modified: 2013-02-21 16:00 UTC (History)
3 users (show)

See Also:


Description Anne 2013-02-21 15:42:28 UTC
Seems cleaner and more readable. (With apologies to Hixie.)
Comment 1 Boris Zbarsky 2013-02-21 15:44:43 UTC
There are non-readonly unforgeable properties.
Comment 2 Boris Zbarsky 2013-02-21 15:47:10 UTC
Well, depending on how exactly you want to define Location, I suppose.
Comment 3 Boris Zbarsky 2013-02-21 15:47:50 UTC
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.
Comment 4 Anne 2013-02-21 16:00:35 UTC
Ah yeah. I forgot we put it on the interface object there. Mkay.