In many instances, the mobile Web is broken in Firefox. We need to understand the scope of the problem and require the capability to track the progress of our various other compatibility initiatives.
To provide the capability to answer scope questions related to the mobile Web such as:
- What percentage of sites have a mobile version?
- What percentage of sites serve their mobile version to Firefox? Chrome? Safari?
- What percentage of sites make use of Webkit specific CSS properties without using the equivalent unprefixed properties?
- What are the most common Webkit specific CSS properties in use?
The scope of Spade v1 is detailed in the P1 requirements on the mobileWebEvangelism-tools etherpad.
Minutes and Progress Reports
list required competencies for people and, once defined, the people working on project. note that not all of these competencies will be required for every project
|Project Champion||Tony Chung, Lawrence Mandel|
|Program Management||Lawrence Mandel|
Spade requirements brainstorm is detailed on the mobileWebEvangelism-tools etherpad.
- P1 automatically feed in a bunch of sites from a file
- P1: tool can parse out css properties if the site is using them and tell us what they are
- P1: tool can determine what User Agents the site is sniffing
- P1: Metrics reporting: https://wiki.mozilla.org/Mobile/Evangelism (See "Tracking Progress Though Effective Metrics")
- P2: Compare results against other browsers (fennec, Chrome Android, Stock Android, Safari Iphone)