On 3 April 2012 18:18, Anthony Hughes <ahu...@mozilla.com
> Great post, Damon. I think this strategy makes a lot of sense. I'm excited
> to see how Kilimanjaro takes shape and to contribute to this effort from a
> QA standpoint.
This *IS* very exciting. My team is currently building products, both for
stack. No Flash, No Java, No plugins, No Native "Apps".
engine (via Apache and our FOSS platform, GPSEE). We officially support
only the latest version of any browser (we are on board with the fast
release train! ... but might need to graft in IE9 support shortly).
We are heavily invested in non-desktop browsers also, meaning we
specifically target GoogleTV Chrome, iOS Safari, Blackberry PlayBook Webkit
along with our desktop support. Android Firefox is on our short list to
add to our test suite -- we used to test Mac OS Fennec before the Native UI
Many of our key application components rely on CSS3 features, and we are
starting to use new HTML5 features as they stabilize and become available.
In fact, yesterday, we did our first "live trial" of photo booth software
which uses webcams via WebRTC -- we are using Chrome Canary (like Firefox
Aurora) builds for this at the moment, but we are confident that WebRTC
technology will make it into the marketplace at large... and hopefully
Firefox Mobile. :)
This post was great, now I have a name for the convergence of events that I
have been describing in the board room (although my POV is more web-wide).
The Kilimanjaro Event is the moment I have been talking about for a long
time, now I can finally give it name. As Mozilla achieves this milestone, I
am confident that it will have a profound ripple effect throughout the web
as a whole, propelling the web forward, just as Phoenix/Firebird/Firefox
did and continues to do.
Wesley W. Garland
Director, Product Development
+1 613 542 2787 x 102