25907 2014-05-28 07:43:48 +0000 Need initMessageEvent method because https://github.com/whatwg/dom/commit/333b03cf6454e803d6433673c33f1292821dac0a 2014-09-11 23:13:22 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#messageevent P3 normal Unsorted 1 contributor ian annevk crimsteam ian mike zcorpan contributor oldest_to_newest 106895 0 contributor 2014-05-28 07:43:48 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/comms.html Multipage: http://www.whatwg.org/C#messageevent Complete: http://www.whatwg.org/c#messageevent Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: Need initMessageEvent method because https://github.com/whatwg/dom/commit/333b03cf6454e803d6433673c33f1292821dac0a Posted from: 90.230.218.37 by simonp@opera.com User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.114 Safari/537.36 OPR/22.0.1471.40 (Edition Next) 106908 1 annevk 2014-05-28 11:21:41 +0000 It seems Gecko successfully removed that method. Why should we add it? I don't think things need to make sense for document.createEvent() users. 106909 2 zcorpan 2014-05-28 11:56:53 +0000 I mean sites that use document.createEvent('messageevent') will most likely break if initMessageEvent doesn't exist. But if Gecko's experience is that the breakage is small enough and Blink is successful with removing it also, then sure, but then I think there's no point in having document.createEvent('messageevent') in DOM either. 106910 3 zcorpan 2014-05-28 11:58:39 +0000 https://bugzilla.mozilla.org/show_bug.cgi?id=848294 https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/H6lsGFqdy3Y 106915 4 crimsteam 2014-05-28 13:12:33 +0000 Its strange that this list was extended: https://github.com/whatwg/dom/commit/333b03cf6454e803d6433673c33f1292821dac0a Before we have only: CustomEvent Event MouseEvent UIEvent Now: CustomEvent Event KeyboardEvent MessageEvent MouseEvent TouchEvent UIEvent Event, MouseEvent and UIEvent has defined init*methods in D2E spec so still may be acceptable. Now DOM (only for Event and CustomEvent) and D3E (draft) define some other init*methods: https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#legacy-event-initializers The level of support these methods by different browsers is really chaotic and probably the only constructors finally change this situation. Without dedicated initializer we can only use universal initEvent() and dispatch this event, but in practice (without posibility set some properties) its nonsens. And for TouchEvent we have this in spec. (https://dvcs.w3.org/hg/webevents/raw-file/v1/touchevents.html#h_note_3): "Some user agents implement an initTouchEvent method as part of the TouchEvent interface. When this method is available, scripts can use it to initialize the properties of a TouchEvent object, including its TouchList properties (which can be initialized with values returned from createTouchList). The initTouchEvent method is not yet standardized, but it may appear in some form in a future specification." So still without any details of how such a method should look like. In general adding more events for document.createEvent() but without dedicated initializer method (which are supported by browsers in the same way) is realy strange, especially if the trend is to remove (or limit) init*methods and use only constructors. 106918 5 annevk 2014-05-28 13:33:23 +0000 They were added because zcorpan reported usage of them in the bug associated with that change. I don't think that necessarily means we have to add corresponding init*Event() methods back. If they can stay gone, that's fine. If that means we try removing "messageevent" as argument again, fine. This part of the specification is still a bit experimental as it's only been a few years since we switched away from this model. 106930 6 ian 2014-05-28 17:57:33 +0000 Is there any point to creating the event that way if it can't be initialised? 107107 7 zcorpan 2014-06-02 05:55:41 +0000 https://github.com/search?l=javascript&q=createevent+messageevent&ref=searchresults&type=Code 19,392 https://github.com/search?l=javascript&q=initmessageevent&ref=searchresults&type=Code 19,393 It seems to me that sites that use createEvent('messageevent') always also use initMessageEvent. 107144 8 ian 2014-06-02 18:15:33 +0000 That makes more sense. 109971 9 contributor 2014-08-05 22:33:45 +0000 Checked in as WHATWG revision r8711. Check-in comment: Add initMessageEvent() http://html5.org/tools/web-apps-tracker?from=8710&to=8711 109984 10 annevk 2014-08-06 08:26:35 +0000 "in <span>MessagePort</span>[]? portsArg" "in " has been obsolete for a long time. "<span>MessagePort</span>[]" should become "sequence&lt;<span>MessagePort</span>>" 111412 11 contributor 2014-09-11 23:13:22 +0000 Checked in as WHATWG revision r8760. Check-in comment: Fix IDL for initMessageEvent() http://html5.org/tools/web-apps-tracker?from=8759&to=8760