This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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?
For this specific case (sequences), I think we should allow a default value. See also bug 25391.
Travis might need such a hook to define keyboard events.
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.)
So why isn't bug 25391, = [] , enough? (Or change the SomeEvent to use sequence<DOMString>? and default to null)
It seems this is taken care of now through changes in IDL.