On 11/28/2015 11:36 AM, Anne van Kesteren wrote:
On Sat, Nov 28, 2015 at 9:09 AM, Ian Young <i...@iangreenleaf.com> wrote:
Maybe a
Mozillian could drop in and give us an explanation of how the W3C
process influences what gets implemented and when?
Well, it doesn't really, many things are standardized by the W3C that
are a poor fit for browsers. What gets implemented depends on what we
think is good for the web, competitive pressure, and available
resources. Having said that, many Mozillians believe this particular
technology is good for the web and there is some competitive pressure,
so it's mostly a question of resources. If you have funds or browser
engineering chops, patches welcome.
It is also about having a good spec to implement. As far as I see, the current
spec is more like a
initial draft.
Stuff like
"obtain U2F MessagePort in a browser specific manner" don't sound good.
So far I haven't found a spec which defines how to get access to U2F
MessagePort or some
u2f object which has register() etc methods.
But perhaps I'm not looking at the right specs.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
