Intent to implement seems premature. Why wouldn't we wait to see how
this goes and let Google do that. I really dislike the idea of rushing
into this API.
A programatic API that does something like AppCache is a good idea --
only in that it is better than the declarative shit AppCache is. We
know (have data, getting more) that AppCache isn't used by the top 50k
sites (it is probably only used in WebApps). IMO, We need more data to
show that this API is more important than the n number of other things
Mozilla wants to implement.
I would feel much better if we "continued to monitor" this api and not
rush here. Let Google do the rushing, lets implement later.
Didn't Jonas have a proposal for the 'offline' use case?
Regards,
Doug
Ehsan Akhgari wrote:
We're planning to implement a prototype of the NavigationController
interface (see bug 898524). We will try to get feedback from web
developers on the prototype and will use that feedback to change the spec
and the implementation and iterate on the API. Our major goal for now is
coming up with a good API that is useful for the intended use cases. Once
we're there, we will talk about plans to ship the API. For now, all of
this work will be disabled for web content.
Please let me know if you have any questions!
Cheers,
--
Ehsan
<http://ehsanakhgari.org/>
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
