- From: Chris Dumez <notifications@github.com>
- Date: Tue, 03 Jan 2017 10:07:28 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 3 January 2017 18:08:07 UTC
As I said, we have no evidence of actual Web breakage. Sadly, there are a lot of WebKit-specific apps / extensions calling initEvent() with a single parameter. We usually deal with this by adding quirks until those apps get fixed. However, in this case, it seems to be a common pattern and it is breaking a lot of iOS apps. I agree that this is not a very compelling argument to get the specification changed but Alex thought it was worth trying given the pain we're currently experiencing. Also note that those 2 boolean parameters are not required when you use the Event constructor (i.e. You can call the Event constructor with only a type) and those have default values (false) for the constructor. Therefore, having initEvent() behave similarly wouldn't look too surprising. -- 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/387#issuecomment-270180752
Received on Tuesday, 3 January 2017 18:08:07 UTC