26101 2014-06-16 05:29:10 +0000 say what to do with event initializer dictionaries that have members without a default value 2014-10-14 11:58:42 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified All All RESOLVED WORKSFORME P2 normal --- 1 cam annevk bugs bzbarsky mike travil www-dom public-webapps-bugzilla oldest_to_newest 107833 0 cam 2014-06-16 05:29:10 +0000 If we have this: dictionary SomeEventInit : EventInit { sequence<DOMString> values; }; [Constructor(optional SomeEventInit eventInitDict)] interface SomeEvent : Event { [Cached] readonly attribute sequence<DOMString> values; }; assuming that [Cached] is a thing, then http://dom.spec.whatwg.org/#concept-event-constructor doesn't handle what to do when the values dictionary member is not present, for example if you do: new SomeEvent({}); Maybe the http://dom.spec.whatwg.org/#concept-event-constructor algorithm allow prose in other specs to describe how the Event object members get their values in this case? 107834 1 bzbarsky 2014-06-16 05:43:34 +0000 For this specific case (sequences), I think we should allow a default value. See also bug 25391. 107836 2 annevk 2014-06-16 06:09:17 +0000 Travis might need such a hook to define keyboard events. 107837 3 annevk 2014-06-16 06:46:07 +0000 Suggestions welcome on how to define this by the way. "default value for attribute /x/" or some such? (Should we also update the specification to more clearly indicate the internal properties of an event are being set (as the exposed are readonly)? Not sure how to do that though.) 107840 4 bugs 2014-06-16 09:22:33 +0000 So why isn't bug 25391, = [] , enough? (Or change the SomeEvent to use sequence<DOMString>? and default to null) 113097 5 annevk 2014-10-14 11:58:42 +0000 It seems this is taken care of now through changes in IDL.