We added two new pages to our wiki on GitHub today: browser compatibility and coding standards.
The browser compatibility has been a long time coming and necessary for any web framework, it just took us a bit to test everything. While developing F2.js, it is an important goal of ours to ensure browser compatibility across the major (and minor) browsers. Of course, creating—and iterating on—a complex and modern web integration framework means taking a forward-thinking approach. As such, you may have noticed we're not officially supporting IE7 or below. This was an important and necessary choice for the F2 roadmap. If you're building a web app that needs to support IE7 and you're running into an issue with F2.js, reach out to us—we'll see what we can do to help.
The coding standards page has also been in the works for a while and is important for the folks contributing to F2. (Thank you!) Coding standards promote a common vocabulary and syntax so that our fellow developers can concentrate on what you're saying rather than on how you're saying it. The standards are based on Google's well-defined guidelines with a few exceptions, and they match the style guide we follow within our 110-person development team at Markit On Demand. If you're contributing to F2, please take a few minutes to become familiar with our coding standards.