29383 2016-01-20 13:22:07 +0000 Need a way to define toJSON, valueOf, @@toPrimitive 2016-01-29 01:56:56 +0000 1 1 1 Unclassified WebAppsWG WebIDL unspecified PC All RESOLVED WORKSFORME P2 normal --- 27361 29183 29384 1 annevk cam bobbyholley josh mike public-script-coord public-webapps-bugzilla oldest_to_newest 124643 0 annevk 2016-01-20 13:22:07 +0000 We want to get rid of [Unforgeable] for Location (the only interface to use that annotation as far as I know), but we do not want to lose out on basically nullifying these properties. As we change this setup, we should also consider making them no longer enumerable as per bug 27361. This subsumes bug 29183 in a way. Perhaps a good general solution would be to allow specifications to define data properties. This has been requested now and then, perhaps now is the time. https://github.com/annevk/html-cross-origin-objects has some additional context as does bug 29376 comment 7. 124673 1 annevk 2016-01-22 14:41:16 +0000 See also https://github.com/annevk/html-cross-origin-objects/issues/21 by the way. There might be more properties here that warrant some kind of override. 124735 2 annevk 2016-01-29 00:33:46 +0000 The way I plan to do this for now is by simply defining these properties in prose when the Location object is allocated. 124737 3 annevk 2016-01-29 01:56:56 +0000 Resolving this as worksforme. If we want to add data properties in IDL that will need its own justification.