Skip to content
Project Platform Status
JavaScript CSS HTML
Branch: master
Clone or download
Latest commit 1970dea Sep 20, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
engine Use new website to retrieve Firefox infor… Jun 15, 2018
features feat: Add “MathML” Sep 19, 2019
routes added gulp build to translate from es6 Mar 9, 2016
src changed browser and favicons to new Feb 2, 2018
tests Fixing tests for travis. Selenium still failing locally. Jul 25, 2016
.editorconfig Adding editorconfig with sane defaults Nov 19, 2015
.eslintrc Disable some rules added by new eslint-config-airbnb rules Dec 3, 2017
.gitignore Add .DS_Store to gitignore Jan 16, 2016
.travis.yml Add Mozilla Code of Conduct (#576) Mar 30, 2019 Update Jan 16, 2018
LICENSE Initial commit. Oct 7, 2015
Procfile Fixing heroku review builds not picking up the latest changes. Nov 24, 2015 Fix devDependencies URL Dec 3, 2017
app.js Call next when we don't have to redirect Apr 22, 2016
app.json Fixing heroku Apr 29, 2016 Add contributing page. Nov 20, 2015
gulpfile.babel.js Fix 'import/first' lint errors Dec 3, 2017
package-lock.json Use 'slugify' instead of 'slug', since 'slug' is no longer actively m… Dec 3, 2017
server.js Fixing tests for travis. Selenium still failing locally. Jul 25, 2016

Project Platform Status

Build Status dependencies devdependencies

tomayto, tomahto, or also platform-status


Platform Status gives developers a cross-platform and cross-browser roadmap for browser features, from standardization and development to release. Not only a channel to raise awareness, it can also drive adoption and improve the vital feedback loop Firefox's platform needs to have with web developers. For most developers it will be a reference to discover and learn, but it has the potential to provide the entry points for radical participation on Mozilla's platform development.


Existing web compatibility references, like caniuse focus on cross-browser compatibility but don't cover un-released features and lag behind on features that already shipped. Major browser vendors (Edge, Chrome, Webkit) are publicising their own platform status with references to their bug tracking and bug owners. Similar to Platform Status' goal, Chrome tracks consensus/enthusiasm from other browsers using sources that range from bugs, to IRC logs to tweets.

Platform Status can send an open and clear message to developers about the state of Mozilla's platform, from proposals of new web features to release.

What is success

  • Developers discover new platform features early in the process, try them out and provide feedback
  • Developers adopt bleeding edge standards because they get clear signals from browser vendors
  • Firefox platform team and a community can maintain the data with low effort

Additional Attributions

Portions of the status data are from (CC BY 2.5), (CC BY 2.5), and (LGPL). Link Closed icon by Thomas Helbig from the Noun Project.

You can’t perform that action at this time.