- Bugfixes around preventDefault not being honored in IE
- Begin the audit of event fidelity
- First step: Begin converting the Syn tests to use testpages, rather that creating, testing and destroying elements.
- Why is this important?: Converting to testpages will allow the same test targets to be used easily by either funcUnit or a human, which we can use to ensure accuracy of event order and types.
There were some questions in the chat about being able to track events on a page. I realize that my description of the tools probably wasn't thorough enough. The tool that I was using is in Chrome Developer Tools, its called "Timeline". Its basically a record and end, will capture any events during that time. Then you can zoom in on different timeframes. It will capture all interactions, and the events that it generates. Here's what it looks-like:
Hope this helps!