Re: [whatwg/dom] document.createEvent() supports lots of events that most UAs do not support initializers for (#362)

> @domenic, do you know why Chrome supports so many event types from createEvent() even though it has no initializer? Would you have a problem with not supporting these in createEvent() anymore?

As flattered as I am being your go-to person for Chrome questions, @foolip is probably a better choice, as he's closer to the implementation work :). In this case I think I can anticipate what he would say though. From what I understand, for a long time Chrome automatically made all events that were added automatically work with createEvent(). Recently @foolip locked that down so that new ones no longer get added to the works-with-createEvent list, freezing that list in place, and he's hoping to over time drive that list down to the one that matches the spec.

It seems plausible to me that Chrome would be able to cut down the list even more, especially if in practice createEvent()ing these events is useless due to lack of init*Event(), but I'll defer to @foolip there.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/362#issuecomment-257628252