Closed digitarald closed 8 years ago
possibly ambient light sensor api http://www.w3.org/TR/ambient-light/
Features with positive developer feedback from chrome:
a few others that come to mind: requestautocomplete - https://bugzilla.mozilla.org/show_bug.cgi?id=1018291 Also some manifest related issues that may not have bugs filed yet - from fxos 2.6 backlog https://docs.google.com/presentation/d/1b6SBgBmI8AcANJGHT37b3Va6m1YNX6P5kEEcJg6lEgw/edit?usp=sharing: Manifest property: theme_color Manifest property: display - currently not fully supported Manifest property: orientation Manifest property: splash_screens Manifest fetch Manifest update
A few random other things on Gecko's radar:
Page transitions <link rel=prerender> (aka prerendering) Media Session FileSystem Screen Orientation Streams IndexedDB Observables Permissions API
@overholt what is the browser consensus on FileSystem
?
@overholt also, what would be the platform take on tracking stale feature development like requestautocomplete?
FileSystem is seen favourably AFAIK but that's perhaps not fair as it's not yet ready for much comment. Stale features are still worth tracking IMO as long as it's not too much work.
Chrome has different entries for "Permissions API" and "Permissions.request() and Permissions.revoke()". What should we do?
We should probably split them out, too, given the split we've got in https://bugzilla.mozilla.org/show_bug.cgi?id=1105827 (.query being done now and .request/.revoke being done later) and this discussion on dev-platform: https://groups.google.com/d/msg/mozilla.dev.platform/7RnCrXoXdG4/Oy84atEoKgAJ
Let's simplify for v1 and just add Permissions API, leaving the 2-tiered hierarchy for v2.
Filed #127.
We are close to 100% of the shortlist - @overholt, would you help checking high-level consistency of the data so far on https://mozilla.github.io/platatus/ and if it reflects Mozilla properly (not so much others)?
A few comments:
Otherwise, looks great!
All addressed in #137, except Custom Elements and IE Streams as that is data coming from external sources. We could override the status on our side or allow adding footnotes?
Footnotes may be worth it since it looks like they're shipping things that we're not but there's more nuance here.
done for v1, backlog should guide us to file more features
Follow up for https://github.com/mozilla/platatus/issues/26 , we will update this bug description as new ideas get added.
Shortlist
:video_game: - requested by games team :package: - by app initiative :exclamation: - piecemeal implementation/hard to track
Backlog